2.35. PIPES

These log messages refer to the PIPES category.

2.35.1. [ID: 1393] Out of non-uniform memory

Log Categories
PIPES,SYSTEM
Log Message
Out of non-uniform memory.
Default Log Severity
Alert
Parameters
pipe, memusageinactive, memusageactive, numinactive, numactive
Explanation
The system was running out of memory needed to honor the traffic shaping policy, likely due to a high number of groups becoming active. Groups that were already active would continue functioning according to policy, but traffic belonging to new groups was instead erroneously forwarded as non-grouped traffic.
Gateway Action
Ignore
Action Description
The system was running out of memory needed for traffic shaping. Traffic that should have been forwarded per group basis was instead erroneously forwarded as non-grouped traffic
Proposed Action
Investigate why the system is low on RAM, though in this particular case it should be obvious that memory was used up by traffic shaping. Complex configurations with many priority levels require more memory. Every active group will consume additional memory, and inactive groups are allowed to keep memory during a grace period. The setting TrafficMgmtSettings:MaxPipesMemUsage can be decreased in order to limit the number of active groups. Also consider adjusting the configuration to lower the maximum number of groups handled by traffic shaping, either by narrowing down the traffic that is grouped or by modifying the grouping parameter. Note that the cost of each group is amplified by the number of precedence levels enabled by the pipe; try to make the best use of the PrecedenceMin and PrecedenceMax parameters. Static group limits (such as UserLimitBpsTotal) also increase the cost per group.

2.35.2. [ID: 1396] No longer out of non-uniform memory

Log Categories
PIPES,SYSTEM
Log Message
No longer out of non-uniform memory.
Default Log Severity
Information
Parameters
pipe, memusageinactive, memusageactive, numinactive, numactive
Explanation
The system is no longer out of memory. Traffic is once again forwarded according to traffic shaping policies.
Gateway Action
Ignore
Action Description
None
Proposed Action
None

2.35.3. [ID: 1416] Pipe memory limit reached

Log Categories
PIPES,SYSTEM
Log Message
Pipe memory limit reached.
Default Log Severity
Warning
Parameters
pipe, numselected, memusage, memusagelocal, memusageactive, memusageinactive, numactive, numinactive
Explanation
The system has reached the memory limit for traffic shaping; some (numselected) active groups of pipe pipe was demoted to inactive state in order to keep within the configured memory limits. Traffic shaping was at this point using memusage bytes of memory, of which memusagelocal bytes were in use by this particular pipe.
Gateway Action
Ignore
Action Description
The system has reached the memory limit for traffic shaping. Traffic that should be forwarded per group basis may be erroneously forwarded as non-grouped traffic
Proposed Action
This log message is normally caused by abnormal behavior such as D-DoS attacks or malfunctioning hardware that is flooding the network with random credentials. In the case where this log is generated by legitimate network conditions, consider adjusting TrafficMgmtSettings:MaxPipesMemUsage and make sure that statistics-per-group is not enabled by the pipe in question. The system will demote randomly selected active groups to handle this situation. Note that the cost of each active group is amplified by the number of precedence levels enabled by the pipe; try to make the best out of the PrecedenceMin and PrecedenceMax parameters. The system will assume that inactive groups can be ignored with regards to memory consumption. The number of inactive groups is indirectly limited by the number of flows, as inactive groups are removed when no flows are using them. Inactive groups can therefore be seen as a property of the flows themselves, and the number of inactive groups can therefore only be decreased either by lowering the number of open flows, or by configuring the pipes to use a more coarse grouping scheme.