I have been trying to figure out a way to control my MSA1000 through the ACU. I would prefer to use the ACU versus hyperterminal using the CLI to configure SAN. I also don't want to dedicate another piece of hardware running windows 2003 just so we can configure the san once in a while. Would a dual boot system make sense in this situation? Does anyone have a guide or steps for dual booting windows and ESX? Also this is a lab\qa environment not production.
What server hardware are you using? If it's an HP Proliant for example the version 7.7 Proliant Agents for ESX3 plus the cpqacuxe application will allow you to manage the MSA from the Management Homepage.
If Proliant and you want more then repost.
This is only true if you have qlogic adapters. Emulex adapters will not allow you to configure the MSA.
If all else fails, I tend to connect the serial cable that comes with the MSA to the back of one of the ESX servers. Install minicom and lockdev (minicom dependency) from rpmfind.net for Fedora Core 1 (Which is close to RHEL3) and use minicom to access the serial console of the MSA. Granted it is not graphical but everything you need is there. The serial port ID is either /dev/ttyS0 or /dev/ttyS1. For the 580 I think it is ttyS1. Launch minicom using 'minicom -o' from the service console and first configure its baudrate, port, etc. per the MSA cable (it is written on there). Then you can hit return and connect.
Note the cable is a special 10 pin cable so do not think it is ethernet.
I think you may be confused about what dual booting is . . .
Dual booting means that both a Windows partition and an ESX partition exsist on the server. At poweron you can choose to either boot Windows or ESX, but not both.
In this case whenever you want Windows running you would have downtime on all of your ESX hosts.
I understand what dual booting is. I would like to control the MSA through the ACU once in a while in my Lab\QA environment. So if I need to take down an ESX server for 15 minutes one day it would not be a production down issue. I know you cannot boot both OS's at the same time it is one or the other. I am trying to provide the logic of why I would want to dual boot the server and I am looking for advice on how to do it. I don't want to user the CLI each time I need to make changes.
The systems management homepage is a browser application that comes along with the install of the HP agents. After install you sit at your workstation browser, point it at https://:2381, login as root and a link to the ACU will be there if you have installed the components from my previous post. You dont need to use the CLI.
If you have a QLogic adapter then the ACU option off the SMH will work. However, if you have anything else then it will not. I use Emulex and have no luck. ESX does not export all functionality of the HBA to the host, so upgrades may not be possible but I have never tried that. I always use the CLI as I only use Emulex in this shop. The other option is to not 'Dual' Boot but to just boot from the MSA CDROM that came with the MSA. You can do that on any machine connected to the MSA.
So I installed the agent and I can get to ther webpage. I then installed the cpqacu from the tmp directory adn then restarted the esx server. I browsed to the webpage and I am still not seeing an ACU option. I can view the storage but cannot control it. Any suggestions?
I installed cpqacuxe using the command
rpm -i cpqacuxe-7.70-12.linux.rpm
Rebooted and doesn't seem to work?
I have confirmed I have qlogic cards QLA2340
Why not just build a 2K3 VM on your ESX server connect to the serial port on you physical server and use the RJ45 to Hyper terminal into your SAN? You could do that and it seems like it would be less work.
To verify that this machine can actually access the MSA properly for management I would boot from the MSA cdrom and see if you can manipulate the SAN. If you can then the Service Console VM can not access Lun 0 (The MSA) and you will not be able to manage it via the ACU.
I would actually put a call into HP and see if they have a solution. It has worked but I no longer remember the exact combo.
While I understand your dislike of the CLI, it is a very easy and intuitive tool. It will also give you a much finer level of control over the LUNs created than the ACU will ever give. I.e. you can make LUNs smaller than disks easily. Use of it in the approach will save you from needed to reboot production servers. The other option is to put a Fiber card into a standard box that can act as your VCB proxy and use it instead. I think most people go this route if they do not want to mess with the CLI. I have never disconnected my cable so no need to mess with it more than once.