Reset Search
 

 

Article

ERS 4950: bcmRx Task Not Releasing Memory Leading To Memory Exhaustion - NVR IMC buffers of size 1612 have been exhausted, buffer pool size 3500

« Go Back

Information

 
TitleERS 4950: bcmRx Task Not Releasing Memory Leading To Memory Exhaustion - NVR IMC buffers of size 1612 have been exhausted, buffer pool size 3500
Symptoms
  • "NVR IMC buffers of size have been exhausted, buffer pool size"  messages occur in logs. 
  • Issue appears to occur only with stacks.
  • LLDP Notification is enabled.
  • System sluggishness.
  • System returns "Cannot modify settings" and "Internal error" messages when attempting to modify an SNMP community string.
ERS4950(config)#snmp-server community ro
% Cannot modify settings
% Internal error

 

  • After rebooting the stack the system doesn't return messages "Cannot modify settings" or "internal error" messages but instead the prompt skips to a blank line and idles.

ERS4950(config)#snmp-server community ro

_

 

  • After about 3 to 5 day after a reboot the system starts displaying the "Cannot modify settings" or "internal error" again when attempting to modify the community strings.
  • When performing a show tech, certain commands that poll information from non base units return with "Internal error".
****Stack Port Statistics****
Unit 2:
% Internal error

Unit/Port Mask Precedence Usage
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
--------- ---------------------------------------------------------------
2/1 % Internal error

 

 

Environment
Ethernet Routing Switch 4950 running software 7.6.2.0
Cause
Issue is due to software defect. System memory is being depleted due an invalid remote logging server associated with the configured IP for the remote logging server.
Resolution

Fix will be addressed in software 7.7.2 tentatively scheduled to be released in April 2020.

Workarounds:
Method 1. Ensure that the IP configured for remote logging is associated with an actual logging server and that IP is reachable.

  • Error state will occur if the configured IP for the remote server is reachable (able to PING) but not an actual logging server.
  • Error state will occur if the configured IP for the remote server is simply unreachable (not able to PING).
  • Error state will NOT occur if the configured IP for the remote server is reachable (able to PING) and the server associated with the IP of the remote logging server is an actual logging server (eg. syslog).

Method 2: Disable remote logging.
1. Disable "Logging Remote" using the command "#no logging remote enable"
2. Save config
3. Reboot 

Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255