When you remove a DAE (Disk Array Enclosure) AFTER you havve removed all LUNs and Raid Groups, you need to reboot the array. I have heard but not confirmed that with the newest flare you only need to restart the Management Server.
The Navisphere Agent needs to be restarted. In flare release 22 and lower, to restart Agent on the array, you need to reboot the array. On flare release 24 and higher, you can restart Agent by restarting the Management Server.
I thought this was correct till I discovered when did restart the management server did not remove the ghost entry. This array was converted from cx300 to cx3-20. Cheers, Prasad Toraty
Every time somebody mentions the word "SAN", I will definately correct him/her. I am so straightforward with that. I'm doing it EVERY TIME. So I hope that they finally will learn that SAN is NOT THE SAME as storage !
I take it this is as much of a pet peeve for you as it is for me?
If a week goes by without some IS architect asking me if we have enough capacity to support their project or if we are going to have to "buy a new SAN" I'd probably die of shock!!!
The worst part is that the architects (who should know better than anyone) are using it wrong in the documentation and then management starts talking about budgeting for a new "SAN".
And when I talk about fabrics their eyes just glaze over
The following action could help you for the issue: Run the following command to both both storage processors (SPs): The command is a customer only command - please contact Support for more information Now restart the Management Server on both SPs
remind that it just apply to flare code R16 and up.
RRR
4 Operator
•
5.7K Posts
0
June 17th, 2008 05:00
kelleg
4 Operator
•
4.5K Posts
0
June 17th, 2008 14:00
regards,
glen
undertaker98
75 Posts
0
June 19th, 2008 03:00
kelleg
4 Operator
•
4.5K Posts
0
June 19th, 2008 07:00
glen
toratyp1
12 Posts
0
June 27th, 2008 04:00
Ta
toratyp1
12 Posts
0
June 27th, 2008 04:00
Cheers,
Prasad Toraty
RRR
4 Operator
•
5.7K Posts
0
June 27th, 2008 07:00
kelleg
4 Operator
•
4.5K Posts
0
June 27th, 2008 07:00
glen
Allen Ward
4 Operator
•
2.1K Posts
0
June 27th, 2008 07:00
If a week goes by without some IS architect asking me if we have enough capacity to support their project or if we are going to have to "buy a new SAN" I'd probably die of shock!!!
*lol*
kelleg
4 Operator
•
4.5K Posts
0
June 27th, 2008 09:00
Allen Ward
4 Operator
•
2.1K Posts
0
June 27th, 2008 09:00
And when I talk about fabrics their eyes just glaze over
kelleg
4 Operator
•
4.5K Posts
0
June 27th, 2008 09:00
glen
Allen Ward
4 Operator
•
2.1K Posts
0
June 27th, 2008 10:00
RRR
4 Operator
•
5.7K Posts
0
June 30th, 2008 02:00
Neo4
7 Posts
0
July 7th, 2008 21:00
The following action could help you for the issue:
Run the following command to both both storage processors (SPs):
The command is a customer only command - please contact Support for more information
Now restart the Management Server on both SPs
remind that it just apply to flare code R16 and up.
Message was edited by:
Neo
Message was edited by: kelleg