No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Key points of Disk Array Installation with M4000 Server in India XXX customer

Publication Date:  2012-07-25 Views:  31 Downloads:  0
Issue Description
This is the first time that the Disk Array usage in India customer, so when start to have installation of HA system with S2600 disk array, we found some points which don't clearly written in the document.

The topology like below:
From topology, we can see connection between M4000 and S2600, there are some fibers and cables connection between them.







Alarm Information
In case 2, the alarm is "can't communication, the configuration failed".
Handling Process
Case 1: No need connect the Mgr port cable of S2600, we can install the Solaris sucessfully;

Case 2: We find one Switcher to connect the Mgr port of S2600 into the DCN, then S2600 configuration is sucessfully;

Case 3: Before change the new multimode fiber, we should shut down the M4000 and S2600 both, then we can change the fiber.


Root Cause
Case 1: When install solaris 10 by quick installation DVD, we also need to do partitioning scheme, but this will be partitioning automatic. And at that time, we connect the fiber between M4000 and S2600, but we don't connect the Mgr port between M4000 and S26000 by cable, that means there is no DCN network, because at the time we don't have HUB or Switcher to make them together;

The Mgr port is for the system configuration level for S2600, when we install the Solaris, the Mgr port connection don't need;

Case 2: When Pre-configuring the U2000, at the time to config the S2600. At the first time, we still don't connect the Mgr port between M4000 and S2600, Then we found the alarm like "can't communication, the configuration failed".

After analyze, we found that we should connect the Mgr port of S2600 to the DCN. When we want to config S2600, there should be communication between the Mgr port IP of S2600 and the NMS server IP, because "AutoSetupS2600.sh" script need Mgr port of S2600 to config. If can't reach the IP, the script can't config, then we have to use mannual ways to config.

Case 3: In the Secondary site, the multimode fiber was stolen and we only can get the temporary fiber at the installation time. After the M4000 & S26000 are running, we get the final multimode fiber, but the machine already running, so how to change fiber? Because the fiber is for the data transmission, if we remove when the server is running, it will create the data inconsistency, then the database will have problem.
Suggestions
null

END