Filter
Top Products
FINAL DRAFT —Cisco Confidential
6-10
Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide
OL-17502-01
Chapter 6 Troubleshooting the Cisco IOS XR Software
Memory Warnings in Configuration Sessions
Clearing a Target Configuration
A low-memory warning can occur when a large configuration file is loaded into a target configuration
session. To remove the target configuration, type the clear command to discard the changes. For
example:
RP/0/RSP0/CPU0:router(config)# clear
Caution Committing a target configuration that has caused a low-memory warning can make the system unstable.
Clearing a target configuration is a preventive measure to not let the system go into a worse memory state
due to additional configuration. In addition, all other active configuration sessions can be closed to
minimize the churn.
Removing Committed Configurations to Free System Memory
You can reduce memory usage by removing configurations from the router, as shown in the following
procedure:
Step 1 Type the show memory summary command in EXEC mode to display the overall system memory:
RP/0/RSP0/CPU0:router# show memory summary
Physical Memory: 2048M total
Application Memory : 1787M (1511M available)
Image: 132M (bootram: 132M)
Reserved: 128M, IOMem: 0, flashfsys: 0
Total shared window: 0
Step 2 Type the show configuration commit list command in EXEC or administration EXEC mode to list the
configurations you can remove.
Note To display the details of a configuration, type the show configuration commit changes command
followed by a commitID number. To display additional configuration history information, type the show
configuration history ? command, and use the command options to display additional information.
Step 3 Type the show running-config command to display the current configuration.
Step 4 Remove configurations as needed to free memory.
For more information, see the Managing Configuration History and Rollback, page 4-6.
Rolling Back to a Previously Committed Configuration
You can roll back the system to a previous committed configuration, as described in Managing
Configuration History and Rollback, page 4-6.