Controller Based WLANs

What are the possible reasons that tmp file size getting increased on the controller?

Aruba Employee
Q:

What are the possible reasons that tmp file size getting increased on the controller?



A:

We might come across the situation that the Controller temp file size seems to be increasing continuously (as shown below) which leads to the controller crash.

 

 

One of the possible reason is that, if there is too many config change and if they are not saved by doing #write memory  periodically  will trigger the increase in tmp file size which leads to controller crash.

Jul  4 09:23:14  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.3.0 255.255.255.0 10.61.0.103 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.34.0 255.255.255.0 10.61.0.134 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.34.0 255.255.255.0 10.61.0.34 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.3.0 255.255.255.0 10.61.0.103 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.3.0 255.255.255.0 10.61.0.3 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.16.0 255.255.255.0 10.61.0.116 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.16.0 255.255.255.0 10.61.0.16 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.11.0 255.255.255.0 10.61.0.11 > -- command executed successfully 
 

Part of the customer design may be to do this route change every second (done by an external script's) and in such case its recommended to add the #write mem command in the script to avoid controller crash due to this increase in tmp file size.

Jul  4 09:23:14  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.3.0 255.255.255.0 10.61.0.103 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.34.0 255.255.255.0 10.61.0.134 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.34.0 255.255.255.0 10.61.0.34 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.3.0 255.255.255.0 10.61.0.103 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.3.0 255.255.255.0 10.61.0.3 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.16.0 255.255.255.0 10.61.0.116 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<no ip route 10.61.16.0 255.255.255.0 10.61.0.16 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<ip route 10.61.11.0 255.255.255.0 10.61.0.11 > -- command executed successfully 
Jul  4 09:23:15  fpcli: USER:admin@10.221.49.102 COMMAND:<write memeory > -- command executed successfully  ===============> Write memory command executed.

 

Version history
Revision #:
2 of 2
Last update:
‎03-26-2017 12:42 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.