Problems after CSM upgrade to version 3.3.1 Service Pack 1

Unanswered Question
Aug 24th, 2010

Hello,

After CSM upgrade to 3.3.1 SP1, automatic IPS signature updates stop working with the following message:

"Unable to communicate with locator service to retrive available files."

IEV has stopped working as well. Error message is in the attachment.

Has anyone experienced similar problem?

Thanks in advance.

Regards,

Vesna

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jia Liu Tue, 08/24/2010 - 16:52

Is 'www.cisco.com' resolved to a particular IP on your CSM server?  You can try changing the DNS entry for www.cisco.com on the CSM server.  Once the host file has been edited and saved, restart the server and try the signature update again.

vciric Tue, 08/24/2010 - 23:57

CSM server uses DNS server for resolving names and proxy server for going to Internet. CSM server goes to Cisco site’s download area without any problem.

Jia Liu Wed, 08/25/2010 - 15:23

From the CSM server, are you able to go to cisco.com and manually download an IPS update sucessfully?

vciric Thu, 08/26/2010 - 00:12

Yes, that always work.

Automatic IPS update has started working again since yesterday, without any reconfiguration on CSM. Do you maybe know what could be explanation for that?

The other issue still persists. After CSM was upgraded to 3.3.1 SP1, IPS Event Viewer cannot be started from CSM. The following error message appears:

"CreateProcess: .\cache\iev\bin\iev-launcher.exe

  https://CSM:443/athena/IEVServlet/user

  C6D7202102ECF1B3A8410987A91D3FF7 C6D7202102ECF1B3A8410987A91D3FF7

  startServerProxy error=267"

Jia Liu Thu, 08/26/2010 - 08:36

I'm not sure what fixed the IPS signature auto update issue but it's possible that there was an issue with cisco.com since no changes were made on your CSM server.

For the IEV issue, can you try un-installing and then re-installing the CSM client?  If that doesn't help, then I would suggest that you open a TAC case since this may be a new issue with the 3.1.1 SP1 code.

qweabab11 Fri, 08/27/2010 - 00:40

jiliu2 wrote:

Is 'www.cisco.com' resolved to a particular IP on your CSM server?  You can try changing the DNS entry for www.cisco.com on the CSM server.  Once the host file has been edited and saved, restart the server and try the signature update again.

I'll try it

Actions

This Discussion