Subscribe
Accepted Solution

OCUM: The overcommitted threshold set at 100% is breached

[ Edited ]

Hi All

 

I dont understand following Messagein OCUM 6.2RC1 with cDOT :

 

The overcommitted threshold set at 100% is breached. 800.00 TB (458.96%) of 174.31 TB is committed. 17.21 TB (9.87%) is used.

sata_overcommited.PNG

 

This mean in my understanding:

When all Volumes mit guarantee NONE will reach the configured Volume Size, I will have a System with 800TB.

 

But when I calculate the Volumesizes I become 29TB and not 800TB:

ListVolumes.png

 

 

Can someone explain me this?

 

TIA Thomas

 

Re: OCUM: The overcommitted threshold set at 100% is breached

[ Edited ]

Hi all 

 

Problem solved. 

Autosize will also count to the overcommited value this is the reason for the overcommited aggr.

 

This is why we get 800TB: 

4x snapmirror (SM) Volume -> max-autosize: 100TB

and

4x snapvault (SV) Volume -> max-autosize: 100TB

 

Solution:

Globally disable "Aggregate overcommitted" in OCUM

Re: OCUM: The overcommitted threshold set at 100% is breached

I solved the problem by alligning the autosize setting with primary controller, manually. 

Re: OCUM: The overcommitted threshold set at 100% is breached

I got the same situation, and feel this parameter is not so much meaningful.

 

So, how can I disable the Global threshold? I know I can edit the volue but no where I can find to disable it.

 

Please advise.

Thanks!

Re: OCUM: The overcommitted threshold set at 100% is breached

 

Hi netappmagic

 

Go to Administration -> Manage Events in your OCUM Webgui and Disable those 2 Events:

 

Untitled.jpg