cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
665
Views
15
Helpful
7
Replies

RME 4.2 -SWIM- SW Distribution - minimum RAM calculation for IOS

Martin Ermel
VIP Alumni
VIP Alumni

Device is a Cisco 7613 Router with native IOS 12.2(18)SXF8.

The calculation of the available RAM size is done while ignoring the amount of shared RAM. With this method the available RAM is only 437 MB. The prerequisites for the image is 512MB. Thus a warning occur.

But on CCO for IOS image prerequisites the total amount of RAM is mentioned. LMS should reflect this situation and should not introduce a new perspective of interpreting the RAM size.

Or does anybody see any sense behind this implementation?

If I do a basic software distribution job I get the following warning:

==============================================

Warning - SWIM1065: Minimum RAM requirement of the selected image: 512 MB .

RAM available on the device ( 437 MB) May not be enough to activate the selected image.

Increase the RAM size for the device, select a different image for upgrading, or

specify the RAM size for the image by editing the attributes of the image stored in the software repository.

Warning - SWIM1201:The selected Flash partition requires a minimum of <512 MB> space to upgrade this image. The current Flash partition space is being increased by <5 %> to the nearest valid Flash size, to accommodate this image.

Warning - SWIM1180: Standby flash does not exist, hence Standby supervisor will not be upgraded with the selected image.

Probable Reason: Standby supervisor may be in ROMMON or not present.

===========================================================

006-02-01-20

---------------------------------

File_Name : s72033-advipservicesk9_wan-mz.122-18.SXF8.bin

File_Size : Unknown

Family : S72033_RP

Version : 12.2(18)SXF8

BOOTROM : 12.2(17r)S4

RAM : 458456384

AliasFamily : C7600S72033_RP

Feature : IP|IPv6|BGP|IS-IS|FIREWALL|VOICE|PLUS|QoS|HA|NAT|MPLS|VPN|3DES|SSH|VIP

Media : ram

Image_Type : SYSTEM_SW

Software_Name : s72033_rp-ADVIPSERVICESK9_WAN-M

SOURCE : disk0:

UPGRADETYPE : ACTIVE

File_Name : s72033-advipservicesk9_wan-mz.122-18.SXF8.bin

File_Size : 82556964

Family : S72033_RP

Version : 12.2(18)SXF8

BOOTROM : 12.2(17r)S4

MIN_FLASH_SIZE : 488

RAM : 458456384

AliasFamily : C7600S72033_RP

MODE : BINARY

Feature : IP|IPv6|BGP|IS-IS|FIREWALL|VOICE|PLUS|QoS|HA|NAT|MPLS|VPN|3DES|SSH|VIP

Media : ram

MD5_Checksum : 0x0

Image_Type : SYSTEM_SW

Software_Name : s72033_rp-ADVIPSERVICESK9_WAN-M

SOURCE : disk0:

UPGRADETYPE : ACTIVE

Flash Information

---------------------------------

Flash Name : sup-bootflash

Flash Size : 65536000

Flash Free : 18864652

Flash Name : bootflash

Flash Size : 65536000

Flash Free : 65536000

Flash Name : dfc#12-bootflash

Flash Size : 15990784

Flash Free : 15990784

Flash Name : dfc#13-bootflash

Flash Size : 15990784

Flash Free : 15990784

Flash Name : dfc#11-bootflash

Flash Size : 15990784

Flash Free : 15990784

Flash Name : dfc#10-bootflash

Flash Size : 15990784

Flash Free : 15990784

Flash Name : disk0

Flash Size : 512024576

Flash Free : 382640128

1 Accepted Solution

Accepted Solutions

A bug was filed a long time ago asking for this (CSCds18146). The bug was closed citing the CISCO-ENHANCED-MEMPOOL-MIB. However, even the objects in that MIB do not provide the actual sum of physical RAM in a device.

View solution in original post

7 Replies 7

Joe Clarke
Cisco Employee
Cisco Employee

Unfortunately, there is no way to get the true amount of physical memory in the device. This is why we do some rounding, and present the user with a warning. The same rounding is now done for flash as well. If there was truly not enough memory or flash, RME would come to a hard error, and would not let you continue.

This warning came about for CSCsd35365. The idea is that we check the amount of AVAILABLE system RAM, and if it falls within an acceptable margin, the device passes. If it is too low, the upgrade will not be allowed.

Currently I cannot test it but what is about ciscoMemoryPoolUsed (1.3.6.1.4.1.9.9.48.1.1.1.5) and ciscoMemoryPoolFree (1.3.6.1.4.1.9.9.48.1.1.1.6) ?

Won't these 2 values together give the total amount of RAM?

Yes, and that's what we use. However, it only gives you the memory available after IOS is loaded. It won't add up to 512, for example.

in the software repository if one would change the settings for 'required RAM' or 'required Flash size' he is bound to the 'usual'memory sizes availabel like 16, 32, 64,128,256,512,.... MB;

As RAM could only exist with these sizes, what about the Idea of rounding up the amount of RAM determined with SNMP to the next useful size? - it is just a quick thought...

perhaps this could be inaccurate as well but I don't think it would be worse as right now

That's exactly what we do. And because it has the potential of being inaccurate, we throw the warning.

The algorithm works like this. Take the amount of RAM collected via inventory collection. If it's less than the required RAM, multiply the required RAM by 0.8. If the device RAM is now equal of greater than that marginal size, throw a warning, but allow the upgrade to proceed. If the device RAM is still less, throw an error, and stop the upgrade.

If the device has EXACTLY the amount of RAM required by the image, throw the same marginal warning (you may not want to overtax the device), but allow the upgrade to continue.

If the device has more RAM than is required, allow the upgrade to continue without a warning.

Ok, it is not obvious at the very first moment if you only see the warning message - but now I see.

Do you know of any plans to implement the 'total RAM size' as *one* Mib value ?

A bug was filed a long time ago asking for this (CSCds18146). The bug was closed citing the CISCO-ENHANCED-MEMPOOL-MIB. However, even the objects in that MIB do not provide the actual sum of physical RAM in a device.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: