DFM is just reporting what's occurring on the 6500 which is InsufficientFreeMemory and that it crossed the threshold defined for the switch. You can check the default values under DFM --> Configuration ---> Polling and Thresholds ---> Managing Thresholds ---> Select Device Type Groups ---> Switches and Hubs and edit. From threshold category, select processor and memory settings. This is where the current values are for the threshold the switch exceeded. If you have modified this, reset values to default .
It seems the alert is cleared after a few minutes and occurr's daily a couple times through out the month. Most likely at that point in time, it has crossed the threshold defined in DFM and generated an alert and after a few minutes its cleared.
1. Take a look at the "show process memory" at the time when problem occurrs and the email generated from this Alert. It should list the "FreeMemoryPct=XXX.xxx %" where the % is the current free memory available.
2. One IOS bug that comes to mind is CSCso05920 which cmpCPUMemoryFree is reported incorrectly for POSIX memory but first you should verify this on the device itself by doing a "show mem" and snmpwalk. Another is CSCsf03710 which SNMP data returned from cmpmemPool reflects only memory usage of the IOS base prcess and the the device as a whole. Both are resolved in the 12.2.33(SXH) train per the bug.
3. If you want, from dfm NMSROOT/CSCOpx/objects/smarts/bin, do a "sm_snmpwalk --community= . This will output three files .walk, .mimic, and snap. Do this when the actual event occurs because it seems the issue clears up after four minutes. And post the content of the alert with the e-mail notification if any to this thread.
Hi, the problem persist, so i send the information generated when the problem ocurrs.
1. Add file with the e-mail alert, the display when run "show process mem" from CLI of box, and information when run snmpwalk from ciscoworks>devicemanager, and the final of document the e-mail when the problem dissapear.
2. Add the files when run "sm_snmpwalk --community=
This is the information you requested, would help us see what happens wtih this alert.
It is possible you are running into a bug if your cli reports different than DFM as far as total and free memory is concerned when running modular IOS on the 6500:
CSCsi10953 Bug Details DFM need way to show Insufficient Memory correctly for Modular IOS Switc
The "show memory" on the new module IOS switch does not show the real memory usage. DFM is using the MIB to poll the exact info of "show memory" and report with the "Insufficient Memory" event.
To display memory correctly, the command "show process memory detailed" is required.
By SNMP, the 'show memory' output is retrieved by using these OIDs ciscoMemoryPoolValid, ciscoMemoryPoolUsed, and ciscoMemoryPoolFree. The total memory is always way smaller than the 'show process memory detailed'.
Using the OID cempMemPoolName from the MIB CISCO-ENHANCED-MEMPOOL-MIB will generate the right result.
DFM will need to start looking into this change. New document or release note is needed for this if a new change is not happening soon.
Set the threshold to the low value to prevent the event from generated.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...