LMS 3.1 - SWIM very slow and finally fail

[Sven Hruza]

Hello,

I have an issue with the SWIM of LMS 3.1 with RME 4.2.0.

The process of software distribution takes very long and finally fails.

For one device (3560 switch) in the LAN the upgrade to IOS c3560-ipbasek9-tar.122-50.SE.tar takes six hours!

But the IOS is not available on the switch, there is no IOS in the flash!

The old IOS was deleted successfully before the copy process.

That's very dangerous, too!

I attached the logfiles of the job.

I use TFTP for transfer.

I tested the original command from LMS for SWIM (TFTP-server is the same):

archive download-sw /allow-feature-upgrade /overwrite tftp://10.10.10.10/c3560-ipbasek9-tar.122-50.SE.tar

The only difference is, that there is no old IOS to delete.

The process works fine and ended successfully after eight minutes.

The output of CLI I attached, too.

The fact, that the IOS will be downloaded twice by using the archive command I know from another thread.

Strange, but okay....works as designed :-)

Thanks!

[Joe Clarke]

You are doing the upgrade over SSHv2, so you may be running into CSCsx24218 (or something similar). You would need to get a full thread dump from the running SWIM job to confirm, though. Therefore, you should open a TAC service request to get the procedure for Windows.

[Sven Hruza]

Thanks for your response!

I will open a case.

[Martin Ermel]

I got a file (patch.zip) that should address the issue of CSCsx24218.

When I uncompress patch.zip I get the following 2 files:

2b975bbd12faabae90d229e9a8a023c2 cmdsvc.jar

d904df59717c01c250bb74eae8802959 xdi.jar

the target location for the files are

NMSROOT/MDC/tomcat/shared/lib/cmdsvc.jar

NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/xdi.jar

Now I have got a litte problem; there is also a patch available that addresses the following 3 bugs:

CSCsv95235, CSCsw39641, CSCsw88378

the patch file is named

326986eef9c9e46801a8623014ddd07e xdi.jar

the target location is the same as above:

NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/xdi.jar

Just applying the files from patch.zip do not resolve the issue.

So which one is the xdi.jar I need - or is there a new one available addressing all 4 bugs???

And what shall I do with cmdsvc.jar ??

Hm ..., I could take cmdsvc.jar from patch.zip and xdi.jar from the other patch...

any suggestion is highly appreciated ...

I just found

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&topicID=.ee71a02&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cd2ab2b

which mentions

CSCsx24218

CSCsv95235

CSCsw88378

to be fixed in one patch. I assume it is xdi.jar - does anybody know the MD5sum?

[Joe Clarke]

The xdi.jar with the MD5 326986eef9c9e46801a8623014ddd07e is mine, and I have rolled all of my fixes for CSCsx24218, CSCsv95235, and CSCsw88378 in addition to CSCsx24218 into this one patch. You just supplement it with the cmdsvc.jar.