WNYVM's Posts

After I opened the ticket w/LSI Support, they said the issue would have to be moved up to development. That was months ago and I haven't heard anything since. Haven't bothered with it to tell the truth. New server builds to deal with and migrations to do, which bring their own issues. Gotta keep movin the ball down field. The alert thing wasn't a show stopper so I moved on. I think I just setup SNMP for the cards and that forwards to one of my syslog servers. That way I'll know if something is amiss. Good Luck

No I could not get the "configure alerts" to work with MSM and get the same error message. I opened a ticket w/LSI a few weeks ago because the issue was reported as fixed in the latest LSI release. Still haven't heard anything back.

Sorry 4 being missing in action lately, Server problems here at the office, bad ones, had me in during off-hours and that's never good. It looks like the script ran successfully. Are you having any issues conntecting? Again I'm using a LSI controller and there isn't any web portion, just the MSM. So I don't have a install log to compare those results to. Diagnostic tools are always your best friend. You can run a /usr/sbin/esxcfg-firewall -q from the COS and how the firewall is configured. You can run trace the packets on the virtual switch for MSM using  /usr/sbin/tcpdump port 3071 -ni vswif0 after you set the switch up to allow promiscuous mode. Change the port number to capute any other traffic you want. Add the -w *.cap (where *=name of file) at the end to capture to a file then you can open in with wire shark or something similar.

Glad to be of some assistance. Reading your original post I sort of figured that was your issue. LSI reccommends that you use the Storelib from the Tarball (choice 1 I think) and not the system. Tech Support is getting lamer and lamer. I have a ticket in w/LSI now for MSM. Nice people and all but usually never get my issues solved. As a aside I would reccommend grabing the MegaRaid Software Users Guide from LSI's website. Compare it to the one you used from Intel and see if it is at least more in depth. Good Luck Greg

I'm not sure about the Intel card or which software is used. The MegaRaid software from LSI says so run the script vmware_install.sh which will guide you through the installation. That script makes calls to other scripts including the one you mentioned. Also after the install you need to create a symbolic link.. ln -sf /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1 I'm thinking maybe you don't have a complete setup. When you do a ps aux at the console do you see the mrmonitor and/or the ~/framework services running? I can't remember where but when I was searching for another issue I think I saw you have to have c-shell installed prior to running the setup. It wasn't from LSI but IBM or Intel I think. But if your running ESX 4.1 you shouldn't have to install it. At least I didn't. Those ports I provided are only for communication between the MSM software. SNMP has it's own ports and you'll need to configure that seperately. Under the /var/log folder there should be a file called MonitorDBg.log. Theres a snmpd.log there too. Open them up and see what's going on. Mega Raid Storage Manager installs under /usr/local usually under a folder w/the same name. You should look in there for logs to. I would uninstall it and use the vmare_install.sh script if it's in the package. Might not be for Intel but it's there from LSI.

Hi Everybody; I came accross this thread tonite when I tried to configure MSM tonite for the first time and hit the same brick wall (no connection). Firstly when doing the CLI install when prompted for "Select the Storelib" use "Inbox Storelib". After my first install (I chose Storelib from MSM package) when I was troubleshooting the no connection part I tailed the /var/log/mrmonitor.debug file and it showed errors, the service would not start. You end up with a libgcc package error. I uninstalled MSM and switched it around and that solved that issue but not the connecting part. After thinking on it a bit it became clear that the issue could be the ports being blocked but checking the firewall on my Computer I saw no entires. Then I came accross this -->> As I suspected. Excuted the following at the console. /usr/sbin/esxcfg-firewall -o 3071,tcp,in,MSM  (make up whatever name you want for the service) /usr/sbin/esxcfg-firewall -o 5571,tcp,in,MSM1 Now I'm in from any computer with MSM. Inside a VM on the same box or another computer on my Network. Cheers Greg