Problem applying IDSMk9-sp-3.0-6-S42

[a.arndt]

Greetings,

I'm trying to update a WS-X6381-IDS IDSM unit that is currently running IDSM-sig-3.0-5-S39 to IDSMk9-sp-3.0-6-S42, but it's not working. The "apply" command works fine, and I can see that the file is being uploaded, but my connection is to the IDSM is being dropped before the patching process begins.

I suspect that I'm having a login timeout or FTP timeout problem, but there's no indication in the error logs to confirm this (i.e. IDSM# (diagnostics) show errorfile idsapply).

Anyone have any suggestions on how I can confirm this?

NOTE: I've successfully updated the unit to IDSMk9-sp-3.0-5-S23 and IDSM-sig-3.0-5-S39 via the same connection without difficulty...

[ywadhavk · Accepted solution]

Hi Alex,

The following FTP servers are supported for service pack and signature updates:

Sambar FTP Server Version 5.0 (win32).

Web-mail Microsoft FTP Service Version 5.0 (win32).

Serv-U FTP-Server v2.5h for WinSock (win32).

Solaris 2.8.

HP-UX (HP-UX qdir-5 B.10.20 A 9000/715).

Windows 2000 (Microsoft ftp server version 5.0).

Windows NT 4.0 (Microsoft ftp server version 3.0).

Is the FTP server one of these?

Thanks,

yatin

[a.arndt]

No it isn't - I was attempting to use Solaris 2.6 actually...

I guess it's time to turn on the FTP server on my NT 4.0 box instead!

Thanks for the help,

Alex

[a.arndt]

Just so anyone who is curious knows, the problem was

actually a combination of two factors:

1) The FTP server where I had the update file posted; and,

2) The speed of the link between myself and the IDSM.

In the case of item 2, the link was only a 128k serial line, so

there was indeed a timeout issue related to BW. I was able

to resolve the problem by uploading the file to another

server (running Solaris 2.7 incidentally) at the other side of

the link and having the IDSM apply the update from there.

Sometimes the simplest solution really is the right one...