FSD Cache Utilization Error
Hi,
I have received an error in SPDC report, saying that FSD Cache Utilization is more than 100% in one of the Aspect server. How to solve this issue?
System version - 800XA 6.0.3
TIA
ATP
I have received an error in SPDC report, saying that FSD Cache Utilization is more than 100% in one of the Aspect server. How to solve this issue?
System version - 800XA 6.0.3
TIA
ATP
Answers
0
One way to deal with it is to increase the cache size.
Node Administration Structure -> Aspect Server Node -> FSD Node Configuration aspect -> Increase LRU Cache size
Node Administration Structure -> Aspect Server Node -> FSD Node Configuration aspect -> Increase LRU Cache size
Answered 5 months ago
0
The output of an SPDC report should always be taken with a grain of salt. The KPIs therein are not always of high importance nor well explained.
There may be some problem with FSD, e.g. obsolete & lingering filesets that flood the cache. In that case, increasing the cache size is not recommended (it would just bloat the disk and postpone the problem for some period of time). There is a freeware called TreeSize Free that can find additional data for you, e.g. which filesets are the biggest hoggers of the cache.
With some tinkering with Windows Explorer you can examine the \OperateITTemp\FsdCache folder's content. Is there some type of files that appear with higher frequency than others? If you e.g. schedule reports on this node and store them in File Viewer aspects, the cache usage can be high for normal reasons. The file extension and content can often lead you to the "bloating" function.
In my opinion, the biggest problem of FSD cache flooding was when Visual Basic 6 was used for process graphics. A saturated cache could delay display callup for operators - but normally, you don't have any operator workplaces running in server nodes. A full cache could also just be "normal operation", the system is making use of all possible cache space set aside for improving performance.
To straighten out the question marks I recommend filing a support case with your regional ABB support center.
The System Version can be 6.0.3.0, 6.0.3.1, 6.0.3.2 or the new upcoming 6.0.3.3.
FSD is embedded in the ABB 800xA Base 6.0.3-0 software kit that came with no rollup on the initial release part System Version 6.0.3.0. Then followed by RU1, RU2, RU3, RU4, RU5 and now lately RU6 (part of System Version 6.0.3.3). Rollups can be dowloaded from ABB Library (an ABB Automation Sentinel license is required).
It is recommended to update to the most recent revision/rollup - in general, it is OK to load a more recent rollup on an older System Version, e.g. ABB 800xA Base 6.0.3-0 RU5 is compatible with System Version 6.0.3.0.
The System Version number does not alone give a satisfactory image of the software installed (as rollups can be added on top) but it will tell what media you installed from and if you are eligible for using Windows 10 and Server 2016 (for which support were added in 6.0.3.1 and 6.0.3.2 respectively).
There may be some problem with FSD, e.g. obsolete & lingering filesets that flood the cache. In that case, increasing the cache size is not recommended (it would just bloat the disk and postpone the problem for some period of time). There is a freeware called TreeSize Free that can find additional data for you, e.g. which filesets are the biggest hoggers of the cache.
With some tinkering with Windows Explorer you can examine the \OperateITTemp\FsdCache folder's content. Is there some type of files that appear with higher frequency than others? If you e.g. schedule reports on this node and store them in File Viewer aspects, the cache usage can be high for normal reasons. The file extension and content can often lead you to the "bloating" function.
In my opinion, the biggest problem of FSD cache flooding was when Visual Basic 6 was used for process graphics. A saturated cache could delay display callup for operators - but normally, you don't have any operator workplaces running in server nodes. A full cache could also just be "normal operation", the system is making use of all possible cache space set aside for improving performance.
To straighten out the question marks I recommend filing a support case with your regional ABB support center.
The System Version can be 6.0.3.0, 6.0.3.1, 6.0.3.2 or the new upcoming 6.0.3.3.
FSD is embedded in the ABB 800xA Base 6.0.3-0 software kit that came with no rollup on the initial release part System Version 6.0.3.0. Then followed by RU1, RU2, RU3, RU4, RU5 and now lately RU6 (part of System Version 6.0.3.3). Rollups can be dowloaded from ABB Library (an ABB Automation Sentinel license is required).
It is recommended to update to the most recent revision/rollup - in general, it is OK to load a more recent rollup on an older System Version, e.g. ABB 800xA Base 6.0.3-0 RU5 is compatible with System Version 6.0.3.0.
The System Version number does not alone give a satisfactory image of the software installed (as rollups can be added on top) but it will tell what media you installed from and if you are eligible for using Windows 10 and Server 2016 (for which support were added in 6.0.3.1 and 6.0.3.2 respectively).
Add new comment