The best way to see why your controller has failed is to look at the Major Event Log. In the major event log, you should be able to see the list of events that happened after you powered on your MD3220. One thing that I can see is that your firmware on your MD3220 is 6yrs old. I have seen some cases that when connecting a new MD1220 to an MD32xx running older firmware can cause issue with controllers showing as offline.
Also, if you have the serial cable that came with your MD3220, then you can connect to controller1 and watch the bootup of the controller to see what is going on as well. Here are the serial settings so that you can see the output on the controller. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).
Last thing is if you have a support bundle from your MD3220 then we can review it to see what is going on with your controller.
Please let us know if you have any other questions.
We contacted the representatives of DELL in our region. Now we are waiting for comments from them. After that, we will try your recommendations and what the representatives of DELL will advise us. I will write the result of all the recommendations. That it remains in the knowledge base. Since this repository is actively used within 24 hours, we can not afford to experiment with its constituents.
Hello. The other day we removed the controller, the indicator continued to light after extraction for another 10 minutes, then went out. Tell me please can the controller hang? Maybe reconnection to the md3220 will start the controller. And the second vopors. Why is the copy speed between the main md3220 and td1220, lower than the copy speed inside md3220?
DELL-Sam L
Moderator
•
7.8K Posts
1
June 15th, 2018 08:00
Hello Dmitriy.Kazinachikov,
The best way to see why your controller has failed is to look at the Major Event Log. In the major event log, you should be able to see the list of events that happened after you powered on your MD3220. One thing that I can see is that your firmware on your MD3220 is 6yrs old. I have seen some cases that when connecting a new MD1220 to an MD32xx running older firmware can cause issue with controllers showing as offline.
Also, if you have the serial cable that came with your MD3220, then you can connect to controller1 and watch the bootup of the controller to see what is going on as well. Here are the serial settings so that you can see the output on the controller. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).
Last thing is if you have a support bundle from your MD3220 then we can review it to see what is going on with your controller.
Please let us know if you have any other questions.
Dmitriy.Kazinachikov
3 Posts
0
June 19th, 2018 20:00
Hello Sam L
We contacted the representatives of DELL in our region. Now we are waiting for comments from them. After that, we will try your recommendations and what the representatives of DELL will advise us.
I will write the result of all the recommendations. That it remains in the knowledge base.
Since this repository is actively used within 24 hours, we can not afford to experiment with its constituents.
Dmitriy.Kazinachikov
3 Posts
0
August 9th, 2018 20:00
Hello. The other day we removed the controller, the indicator continued to light after extraction for another 10 minutes, then went out. Tell me please can the controller hang? Maybe reconnection to the md3220 will start the controller. And the second vopors. Why is the copy speed between the main md3220 and td1220, lower than the copy speed inside md3220?