When you configure the MSM, do not let it discover all the controllers in your network.
Configure it to only see a single IP at a time, and it will work.
You can even start a second instance to log to a second system.
Genius
When you configure the MSM, do not let it discover all the controllers in your network.
Configure it to only see a single IP at a time, and it will work.
You can even start a second instance to log to a second system.
Member
I have similar problem with LSI MSM.
As long as we had Open-E DSS v6, remote LSI MSM could connect to appropriate mgmt IP on storage and logon to LSI RAID controller inside storage.
Now, when we are testing DSS V7 trial on the same system, remote LSI MSM doesn't report any LSI controller on the same mgmt IP on the storage.
Just like there is somekind of firewall activated, or something else.
Senior Member
Originally Posted by Gr-R
Please read again what I wrote before.
Of course we had MSM setup not to discover anything and entered the ip manually.
Again what we did:
We changed the PASSWORD for the user "raid" in DSS V7 WEBGUI in Setup/Hardware Raid,
which made the system unaccessable for MSM !
And this is not reversible !
We have two DSS V7. Lucky, that we did the password change only on one system,
the other system is still accessible via MSM by user "raid" password "raid" as the first system was before.
Regards
Genius
When you start MSM, is it listing both nodes as available to connect to?
This is the problem, force it to list only one, and you should be able to log in. Clear the favorites list, so listing only a single node.
Senior Member
OUCH !
Crappy little piece of sh*tty software....
Thanks a lot, that does the trick.
Regards.
Genius
Indeed.
Something has happened in the latest release of MSM.
Senior Member
Funny anyway, they say they fixed that at least for ESXi 5.0:
http://www-947.ibm.com/support/entry...d=migr-5077712
ROFL !
Regards
Posting Permissions
Reply With Quote