Ever seen this: %% Low on memory; try again later

Answered Question
Nov 30th, 2009
User Badges:

I have a 3750 switch that currently will only display this error:


%% Low on memory; try again later


The only warning/error that is on our logging server previous to this is a traceback error. Thier is no history of this on this stack, and if it was so low on memory I would have expected to see a %memalloc error before a full failure.


Any ideas? At the very least I'm trying to figure out if I have more going on here then simply memory overrun and needing a reboot.

Correct Answer by glen.grant about 7 years 7 months ago

    The other switch will be fine but it will become the stackmaster and it will not fall back to the original switch by itself .   If that is a concern make sure the switch priorities are set  and just reload the whole stack .   We have seen the low memory issue also on a 6 switch stack , we reloaded the whole stack . I think the stackmaster sometimes runs into issues  because it  has to handle  the configuration and tracking of things like spanning tree and other functions for the whole stack .  My take it is a bug and for some reason these  eventually run into a memory leak situation.   Cisco should look into this further but I can't say I have seen a bug  for this and I have looked before .  We run like 12.2.35SE  .

Correct Answer by Giuseppe Larosa about 7 years 7 months ago

Hello Lsimancek,

this message should mean that unfortunately it is high time to reload this device.


I've seen this message on routers. On a switch like yours it should be the sign of a SW bug.


Hope to help

Giuseppe

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Giuseppe Larosa Mon, 11/30/2009 - 13:28
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Lsimancek,

this message should mean that unfortunately it is high time to reload this device.


I've seen this message on routers. On a switch like yours it should be the sign of a SW bug.


Hope to help

Giuseppe

Lsimancek_2 Mon, 11/30/2009 - 13:33
User Badges:

Giuseppe,


Ouch, figured ... reboot it is!


Now here is part 2: This switch is apart of a 2 switch stack, the switch with this error is the master switch, what is the likelyhood that the master switch is the only one running out of memory and the member switch will take over the stack when the current master dies or is rebooted without problem?

Leo Laohoo Mon, 11/30/2009 - 13:36
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

I've seen this error message on a WS-X4013+ and all traffic just ground to a halt.  According to TAC it was a bug in the IOS and I had to upgrade the firmware to fix the issue.

Lsimancek_2 Mon, 11/30/2009 - 13:53
User Badges:

I haven't found a doc yet nor does anyone around here know, so do you guys know if the master switch is having the memory failure should the member switch be fine and take over? Or does having the master switch "lose its mind" negativily effect the member switch?

Correct Answer
glen.grant Mon, 11/30/2009 - 14:20
User Badges:
  • Purple, 4500 points or more

    The other switch will be fine but it will become the stackmaster and it will not fall back to the original switch by itself .   If that is a concern make sure the switch priorities are set  and just reload the whole stack .   We have seen the low memory issue also on a 6 switch stack , we reloaded the whole stack . I think the stackmaster sometimes runs into issues  because it  has to handle  the configuration and tracking of things like spanning tree and other functions for the whole stack .  My take it is a bug and for some reason these  eventually run into a memory leak situation.   Cisco should look into this further but I can't say I have seen a bug  for this and I have looked before .  We run like 12.2.35SE  .

Lsimancek_2 Mon, 11/30/2009 - 14:28
User Badges:

Unfortunately since I can't get in I have no idea if the priorities were set correctly. These were installed by a co-worker long gone. I hope they are, right now our plan is to let them run until wither it reloads itself or I can this weekend.


Thanks for the help!

Leo Laohoo Mon, 11/30/2009 - 14:45
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

The command to check the priorities is "sh switch detail".


If you need to change the priorities it's "switch priority <1 to 15 with 1 as default>".

Lsimancek_2 Mon, 11/30/2009 - 14:49
User Badges:

Yes, but right now the switch is pretty much useless (other then its still passing traffic)  because from console you can't get a prompt. All you see is


     %% Low on memory; try again later 


when attempting to use the switch. The console on the other switch in the stack is unresponsive, so I can't access the device to alter priorities. But thanks for trying

Actions

This Discussion

Related Content