Not Enough Shared Memory for the Interfaces IP Input and CiscoWorks UT Discovery In Packet Memory ("I/O" or " Processor" on high-end routers, "PCI" on 7200 series and VIP cards) Known 70x0 Issue when Loading Large Cisco IOS Software from Flash or Netboot Large Quantity of Memory Used for Normal or Abnormal Processes Memory Size Does not Support the Cisco IOS Software Image Possible Causes In Processor Memory ("Pool Processor" on all Platforms) is the process that was affected by the lack of memory. 7200 series and Versatile Interface Processor (VIP) cards can also report errors in pool Protocol Control Information (' pool PCI ')" for the packet memory. High end routers (7000, 7500 series) have their buffers in main dynamic random-access memory (DRAM), so a lack of packet memory can be reported as "pool processor". indicates whether the processor memory (' Pool Processor ') or the packet memory (' pool I/O ') is affected. = the number of bytes the router tried to allocate, but could not find enough free memory to do so When you do a show logging command, you must see something like this: %SYS-2-MALLOCFAIL: Memory allocation of bytes failed fromĠ圆015EC84, pool, alignment 0 -Process= Īfter you have collected the necessary data, reconnect all of the LAN and WAN links and continue to monitor the memory usage of the router. At minimum, you want to collect the complete output of these commands: show memory allocating-process totals (or show memory summary if show memory allocating-process totals is not available), show logging, and if possible, show technical-support. Are you able to get a response and execute commands? After a few moments, there must be enough memory available to allow the console to respond.Ĭollect the needed information from the privileged EXEC mode (Router#). This can cause the router to stop passing packets. These are the steps to try in order to capture data when the console port is under very low memory conditions:ĭisconnect the LAN and WAN cables from the interfaces on the router. Note: If Border Gateway Protocol (BGP) is configured on the router, you can refer to Achieve Optimal Routing and Reduce BGP Memory Consumption to reduce the memory consumption related to this process. If you help the router free some memory, the console can respond, and you can then capture the necessary data from the router for troubleshooting. There are steps you can take to allow data capture through the console. If you see the previous message, there is not even enough available memory to allow for a console connection. When you connect to the console port, however, you can see this: %% Unable to create EXEC - no memory or too many processes At this point, it is important to get access to the console port to collect data for troubleshooting. When a router is low on memory, in some instances it is not possible to Telnet to the router. "Unable to Create EXEC" Error or When the Console Does Not Respond The console message "Unable to create EXEC - no memory or too many processes" The show processor memory command is displayed no matter what command you type on a console The console or log message: "%SYS-2-MALLOCFAIL: Memory allocation of 1028 bytes failed from 0圆015EC84, Pool Processor, alignment 0" Symptoms of memory allocation failure include, but are not limited to: This can happen with the processor memory (used by the Cisco Internet Operating System ) or with the packet memory (used by incoming and outgoing packets). The memory has fragmented into such small pieces that the router cannot find a usable available block. The router has used all available memory (temporarily or permanently), or Refer to Cisco Technical Tips Conventions for more information on document conventions. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. Note: This document does not apply to Cisco Catalyst switches that utilize CatOS or MGX platforms. The information in this document is based on these software and hardware versions: There are no specific requirements for this document. This document describes symptoms and possible causes of memory allocation failure (MALLOCFAIL) and details on how to fix these problems.
0 Comments
Leave a Reply. |