This article discusses steps to take when starting investigation of an NPM memory usage alarm.An entry similar to the following line is present in "/var/log/messages" file:

cbsalarmlogrd: AlarmID 321735 | Thu Dec 5 08:50:42 2013 | major | np1 | npmOutOfMemory | NPM memory usage

The CLI displays an active alarm for NPM memory usage:

CBS# show alarms active major

This article discusses steps to take when starting investigation of an NPM memory usage alarm.

1. Verify that XOS configuration doesn't contain any old troubleshooting statements: 

• trace option in IP flow rules
• acl-interface and acl-interface-mapping

2. Collect details about the alarm

CBS# show alarms active major verbose

When the alarm isn't active anymore, run this command:

CBS# show alarms history major verbose


3. Telnet to the NPM and capture the following output

CBS# unix su
# telnet npm<N>

cat /proc/meminfo
du -x /
ps
cat /proc/*/status
ifconfig -a
cat /etc/syslog.conf


4. Contact Blue Coat technical support and provide the collected data for review.

Workaround

N/A