Unsolved
This post is more than 5 years old
5 Posts
0
1550
CenteraConsole V2.5 issue with Historic Cluster Capacity
CenteraConsole V2,4 and V2,5 are not reporting the Historic Cluster Capacity correctly. We added new nodes and cubes to our Centera Cluster(s); which increased our "Total Capacity" to 524TB. Centera Console is still reporting the old Capacity; I have restarted all the CenteraConsole Services, Rebooted, and also Upgraded Centera Console from V2.4 to V2.5, no change.
The CenteraConsole option: PERFORMANCE-->CLUSTER CAPACITY-->HISTORIC displays 327TB Total Capacity.
However, CenteraConsole PERFORMANCE --> CLUSTER CAPACITY-->CURRENT is reporting 524TB Total Capacity.
Satish_Kutty
216 Posts
0
June 21st, 2012 02:00
Hi,
Please refer to Primus Solution ID "emc231279" which explians the issue in detail.
Regards
Satish.N.Kutty
Bieckert
5 Posts
0
June 21st, 2012 07:00
Satish,
CenteraConsole V2.4 Historic Capacity Reporting was working fine for almost a year. It’s not a configuration problem; Centera Console is not detecting the 180TB capacity that was recently added to our Cluster; It’s definitely a History Manager function; and it’s configured exactly the same as it’s been since we enabled Historic Reporting in Centera Console. In addition; the CenteraConsole Archive --> Warnings page does not show any connection issues or errors. In addition; I know the History Data is being written to the History Manager database as the DB Size continues to grow….. The Cluster Capacity --> Historic --> Graphical display is showing a Total Capacity value of 327TB…..it should be 524TB…it’s not seeing our new Capacity.
Thank You,
Mark Bieckert
Bieckert
5 Posts
0
July 5th, 2012 07:00
Folks,
I recieved an answer from high-level EMC Centera Support. The issue was not the configuration; which should have been evident since nothing changed in Centera Console, simply new nodes were added. The issue was the Centera Capacity Sensor on both of my cluster's had to be restarted. So, word to the wise, and before anyone tries to tell you have a configuration issue; have EMC Support verify the Capacity Sensor is running.
Satish_Kutty
216 Posts
0
July 5th, 2012 09:00
Hi Mark,
Thanks for the update...
Regards
Satish.N.Kutty
Bieckert
5 Posts
0
July 5th, 2012 10:00
Satish,
You referenced Primus Solution ID “emc231279”, how is that accessed? EMC Internal? Or is it open to the Customer?
Thanks,
Mark S. Bieckert
Lead Systems Programmer/Analyst
Office 713.338.6423
Mobile 281.245.8033
Mark.Bieckert@memorialhermann.org
Information Systems Division
Memorial Hermann System Service Tower - North
920 Frostwood, Suite 2.300.29
Houston, TX 77024
"We can't solve problems by using the same kind of thinking we used when we created them." Albert Einstein
1 Attachment
image001.jpg
Satish_Kutty
216 Posts
0
July 9th, 2012 08:00
Hi,
The Primus ID "emc231279" is Customer viewable; you should be able to access it through Powerlink. I'll mail you the Primus solution if you are unable to access the same.
Regards
Satish.N.Kutty
Satish_Kutty
216 Posts
0
August 15th, 2012 05:00
Hi Bieckert,
Please let me know if you were able to access the Primus ID "emc231279" now.
Regards
Satish.N.Kutty
Bieckert
5 Posts
0
August 15th, 2012 10:00
Yes
Thanks,
Mark S. Bieckert
Lead Systems Programmer/Analyst
Office 713.338.6423
Mobile 281.245.8033
Mark.Bieckert@memorialhermann.org
Information Systems Division
Memorial Hermann System Service Tower - North
920 Frostwood, Suite 2.300.29
Houston, TX 77024
"We can't solve problems by using the same kind of thinking we used when we created them." Albert Einstein
1 Attachment
image001.jpg
Satish_Kutty
216 Posts
0
August 16th, 2012 08:00
Hi,
Thanks for the update.
Regards
Satish.N.Kutty