Ipcheck Values /esa

[spacemeb]

Hello guys,

I was curious about the below values:

Root 400MB 68%
Nextroot 400MB 86%
Var 400MB 3%
Log 179GB 6%
DB 2GB 0%

Can someone please elaborate what each value means? when we should be alert about that?

I see that the next root is 86% in my case at my lab, is this weird? 

I have also encountered root partition which is over 100%. What that means?

Is there anything that we should monitor via these values?

[balaji.bandi]

that is normal as per your output.

I see that the next root is 86% in my case at my lab, is this weird?  - not that i worry about.

I have also encountered root partition which is over 100%. What that means?  - depends on what partition, some time logs consume more space, so you need to delete or auto roll config need to be done, some time this is bug also depends on version.

Is there anything that we should monitor via these values?  - as long as Log Directory not fillled, you are ok.

Hope that help you.

[Ken Stieers · Accepted solution]

Those are the partitions on the disk

Root  = the currently installed/running partition

Nextroot = where the next install/upgrade will go... then root and nextroot are swapped

Var = typically "variable data" that the system needs to write to...

Log = self explanatory 

DB = where the tracking db is stored

Swap = memory swap space

Mail Queue = self explanatory

There was a point where you had to redeploy a fresh vm because new versions of the code are too big for the 400meg root.  They may have gotten around that...

[spacemeb]

There was a point where you had to redeploy a fresh vm because new versions of the code are too big for the 400meg root.  They may have gotten around that...

About that! This is what I was thought as well ..but I was not certain, a confirm would be nice.

I will try to replicate it on lab to see what it will happen..

[Ken Stieers]

I'm pretty sure they fixed it for now... I'm not sure if its going to pop up again eventually.

[SriramV]

nextroot issue was seen in ESA 14.0.0-692

it was fixed in ESA14.0.0-696 and later builds

[spacemeb]

What do you mean? 

[spacemeb]

It was seen in versions before 14 and now it has been fixed??

[dmccabej · Accepted solution]

Hello,

The fix that was put into place in 14.0.x is only a temporary solution. While it allows the upgrade up to 14.0.x, your device will still run into upgrade errors in the future. 

Please review the Field Notice below and work to deploy a new image asap to resolve this issue completely moving forward.

https://www.cisco.com/c/en/us/support/docs/field-notices/722/fn72230.html

Thanks!

-Dennis M.