Always MD5 failures on older hardware with RME

[bnidacoc]

It seems that older products which used to work with CW 2.2's RME have been poisoned to stop working.

The RME>Software Management>Library>Add Images always bombs out adding images for the following older products;

MSFC2 downloading 12.1(27)b.E (Hybrid mode code)

3640 downloading 12.2(34)a

3500XL-EN downloading 12.0(5)WC14 (this code was released this month)

2924XL-M-EN downloading 12.0(5)WC14 (this code was released this month, plus the M is still under hardware support)

Why do I think that somewhere, something has been poisoned? Because RME almost instantly replies with an MD5 checksum failure, much faster than I can actually download the files from Cisco.com. I have never been able to download files from Cisco.com within seconds, but it is only about 10-15 seconds until I get the MD5 failure.

I don't have this problem with newer hardware, like 4500/Sup2/Sup4/Sup5, 6500Sup720s, 2600XM, 2800s, 2950s, 3550s, 3560s, 7500s.

I’m on Common Services 2.2 SP2, RME 3.5 IDU 13.

I believe this is the first time I have ever had MD5 failures downloading via CW/RME from Cisco.com

It sure seems suspicious that this problem ONLY occurs on the older hardware nearing, but not beyond, EOS status.

[David Stanford]

Looks like you might be running into CSCsa81146

In this case RME 3.5 has problems downloading images mainly for Catalyst Switches running IOS images.

Example: 2950, 3550, 3560, 3750

The workaround is to manually download the image from Cisco.com and add to RME-SWIM using "Add from filesystem".

This should be fixed in RME 4.0.1

[bnidacoc]

Thanks, but I don't have a problem with 2950s, 3550s, 3650s, 4500s, or native 6500s.

Also, why would it have a problem with the RP Hybrid code of an MSFC2?

[David Stanford]

when trying to add these images do you see any indication of which link RME is trying to access on CCO to get them?

[bnidacoc]

I can tell you that roughly 1 ms after receiving an HTTP/1.1 200 OK, I then receive a FIN bit.

I'm not going to supply the capture as cisco.com credential encryption is weak. There also appears to be a contract field feedback in the 200 OK response which I wouldn't want released to the rest of the world as well.

[David Stanford]

You might want to open a TAC case for this, its either the same bug I mentioned or it could be that something has changed on CCO with regards to the location of these images

[bnidacoc]

Yea, I suppose... I doubt anything could be done within the next few weeks and our maintenance weekend is in 2 days.....

BTW, I can't DL c2600-i-mz.122-34a.bin, nor the i-mz version 12.3.19 for the 2600 as well. But I can DL the 12.4.8.....

This is almost as bad as it was in 2003. And it did so well last year too after TAC fixed one major problem......

It also won't DL the 12.2(31)SG/Cat4KSup4 code..... But this case is different, it isn't even displayed in the list to download, only the EWA train is displayed.

[GlanvilleP]

Hi,

Just encountered this exact problem. Did you get a fix? If so, can you post it to this thread, please.

I notice that the problem is caused by the IOS file appearing in the CSCOpx\temp folder, size 1k, contents are text telling you that you're not logged in properly. Hence the checksum of this file does not match that of the genuine file. By why am I not logged in???!!!

(updating every module in sight has not helped)

Regards

Peter

[bnidacoc]

No, I don't believe I tried to get a fix for it. This is really a bad situation, it seems that something is poisoning RME 3.5. To encourage people to migrate to RME 4.x maybe?

But RME 4.x reminds me of the high failure rates of RME 3.5 in in 2003. It seems that RME 4.x just isn't ready for production.

A very discouraging situation. I wish that CW LMS 2.5/2.6 suite was as reliable as ACS. I hope Call Manager is as reliable as ACS has been. I hope nothing else fails at the rates CW LMS 2.5/2.6 does.

[GlanvilleP]

Thanks for the Answer.

Tried another search "RME Download MD5" and found an "ask the expert" answer.

They suggest downloading the image and importing to RME by hand.

That would be fine, apart from the fact that in my windows version, WHATEVER I enter as directory path (even simply using the browse button and accepting the default) is rejected as Directory does not exist.

So I agree, it's a strategy to make me buy the upgrade!!

[bnidacoc]

Well, get used to that importing manually process. Even though it doesn't scale, I still have to manually import for newer devices (2600XMs come to mind) in RME 4.0.5, with device updates applied. I've had a case open with TAC for so long now about downloads from Cisco.com, I don't even recall which of all the platforms I have had the problems with.

I am even using RME 4.0.5 for some SW distributions, and RME 3.5 for those which 4.0.5 fails. There was one platform, which both now fail on and I had to upgrade them manually. I *think* that was the IOS 4500/Sup4s on 12.2(25)SG1 going to 12.2(31)SGA in late October 2006. RME 3.5 didn't like SG code, RME 4.0.5 mysteriously wouldn't distribute 12.2(31)SGA to any of the existing SG devices. I had distribute to 9 of them manually.

It is so discouraging, that I asked for this software, and the CW reliability has not been resolved in this new version.