The Management Server is the package that controls the user interface (GUI). When you restart the management server, it resets the objects that Navisphere knows about. If you had an entry that was unknown, it would remove this when it restarted.
In later versions of Navisphere, the Agent program was made part of Management Server, which is why you can restart the Agent now by restarting the Management Server. In the older releases (before release 24) you must reboot the SP to restart Agent.
The tool is for internal use only and will not be released.
The tool to analyze SPCollect is for EMC internal/partner use only - I am not sure why you need to analyze SPCollect. Are you having any issue or problem?
If you don't see any error on NaviSphere and no warning/error messages on the Alert section - you need not to be worried at all.
However, if you still want to get the SPCollects analyzed, please open a Service Request with EMC CLARiiON support or please contact your EMC CE (Customer Engineer) or the EMC Authorized service person.
Thank you for your response. I am dealing with a problem on cx600 where I see SP B is unmanaged. I would like to know what could be the cause for it.
Wish EMC had this tool available online like HEAT which would help their customers to see the SPCollect report. I hope there is no intelligance inside tool so one has to figure out whats wrong themselves anyway. Hence I guess it would help to see the report in well formatted way atleast.
There are a number of things that cause an SP to go unmanaged. To see what the issue is you need to determine if the SP is hung (stopped) or if Agent is stopped.
1. ping the SP - this will tell you if the SP is still running - if you get a reply, the try
2. navicli -h IP_Address_SP getagent - this will tell you if Agent is running - if you do not get a reply, then Agent is stopped. To restart Agent you need to reboot SP. You should probably contact EMC at this point.
Having Agent stuck will not affect your disk access. There are a number of reasons that Agent can stop - most have been fixed with flare upgrades.
As to the tool, as Sandip mentioned, this is for internal use, it is not intelligent, you still need to know where to look to determine the cause. Before this tool, we just went through the logs, this tool does a lot of the extraction from the ZIP files - just makes it a little easier to get at the files.
Thanks for your reply and I do appreciate your time.
The problem with SP was kind of weired. It was showing a vogue entry of another chassis ( same hierarrchy, host etc, ) and named as "B-UNKNOWN". We had SP rebooted but the vogue entry re-appeared again after few hours. We restarted the management server and don't see that entry so far.
I guess the management server is comman entity for for SPs. Is that right?
I looked at the SPCollect of SPA but couldn't find any errors/warning partaining to the vogue entry telling me why SP B became unmanageble. But I think I am not used to examine SPCollect and thought I could have missed something in the SPCollect. So I thought the tool could have helped me to show some information out of the SPCollect related to the problem.
Is it posssible to share this tool or made available online like HEAT?
kelleg
4 Operator
•
4.5K Posts
0
February 3rd, 2009 14:00
In later versions of Navisphere, the Agent program was made part of Management Server, which is why you can restart the Agent now by restarting the Management Server. In the older releases (before release 24) you must reboot the SP to restart Agent.
The tool is for internal use only and will not be released.
glen
nandas
4 Operator
•
1.5K Posts
0
January 30th, 2009 13:00
The tool to analyze SPCollect is for EMC internal/partner use only - I am not sure why you need to analyze SPCollect. Are you having any issue or problem?
If you don't see any error on NaviSphere and no warning/error messages on the Alert section - you need not to be worried at all.
However, if you still want to get the SPCollects analyzed, please open a Service Request with EMC CLARiiON support or please contact your EMC CE (Customer Engineer) or the EMC Authorized service person.
Hope this helps,
regards,
Sandip
snirmal123
37 Posts
0
January 30th, 2009 18:00
Thank you for your response. I am dealing with a problem on cx600 where I see SP B is unmanaged. I would like to know what could be the cause for it.
Wish EMC had this tool available online like HEAT which would help their customers to see the SPCollect report. I hope there is no intelligance inside tool so one has to figure out whats wrong themselves anyway. Hence I guess it would help to see the report in well formatted way atleast.
Can I get this tool from EMC if I log a case?
Thanks
kelleg
4 Operator
•
4.5K Posts
0
February 2nd, 2009 10:00
1. ping the SP - this will tell you if the SP is still running - if you get a reply, the try
2. navicli -h IP_Address_SP getagent - this will tell you if Agent is running - if you do not get a reply, then Agent is stopped. To restart Agent you need to reboot SP. You should probably contact EMC at this point.
Having Agent stuck will not affect your disk access. There are a number of reasons that Agent can stop - most have been fixed with flare upgrades.
As to the tool, as Sandip mentioned, this is for internal use, it is not intelligent, you still need to know where to look to determine the cause. Before this tool, we just went through the logs, this tool does a lot of the extraction from the ZIP files - just makes it a little easier to get at the files.
glen
snirmal123
37 Posts
0
February 2nd, 2009 16:00
Thanks for your reply and I do appreciate your time.
The problem with SP was kind of weired. It was showing a vogue entry of another chassis ( same hierarrchy, host etc, ) and named as "B-UNKNOWN". We had SP rebooted but the vogue entry re-appeared again after few hours. We restarted the management server and don't see that entry so far.
I guess the management server is comman entity for for SPs. Is that right?
I looked at the SPCollect of SPA but couldn't find any errors/warning partaining to the vogue entry telling me why SP B became unmanageble. But I think I am not used to examine SPCollect and thought I could have missed something in the SPCollect. So I thought the tool could have helped me to show some information out of the SPCollect related to the problem.
Is it posssible to share this tool or made available online like HEAT?
Thanks
Sam