Cisco Cisco Aironet 350 Access Points

If you have a console connection during this type of task failure, warnings similar to the following are 
displayed while the task is running:

Retrieving file "10.0.0.11:UpgradeImage10.0.0.108Jun20.img" via TFTP.

*** Suppressing console event log display due to low memory.

*** Restarting System in 5 seconds...

*** Recovered from low-memory condition. Restoring normal console event log display.

If you do not have a console connection, the only observable symptom is the behavior of the access point 
LEDs, which blink in an unfamiliar pattern.

Make sure that the access point has at least 4 MB of DRAM available per task. To display the amount of 
available DRAM, use the following VxWorks command during a console or Telnet session with the 
access point:

Output similar to the following is displayed:

(Auto Apply On) :BOttom, :Down, :Back, ^R, =, <ENTER>, or [Link Text]: :vxdiag_memshow

This example shows that 3,263,544 bytes (or about 3.2 MB) of DRAM are available (see the number in 
the "bytes" column above). This is not enough DRAM to upgrade an access point running VxWorks to 
IOS software.

You can free some DRAM by:

Terminating non-critical processes.

Setting non-IP related configurations back to the default values.

Disabling extra memory allocations used by some SNMP functions.

Changing some event handling configurations on the access point. Set the maximum number of 
bytes stored per alert packet to 0 and set maximum memory reserved for detailed event trace buffer 
(bytes) to 0. (Making these configuration changes requires that you reboot the access point.)

After freeing DRAM, use the :vxdiag_memshow command to confirm that there is enough DRAM to 
perform the upgrade to IOS software.

status

bytes

blocks

avg block

max block

current

free

3263544

370

8820

2875056

alloc

10061376

5490

1832

cumulative

alloc

11956232

16310

733