Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Senderbase down issue

Hi,

I seem to be having problems with one of our ironport clusters which is displaying 'senderbase down'. We have other ironport clusters on different sites that are displaying senderbase is up and running so i'm trying to diagnose why this site cant access it.

Port 53 is open and I can see dns traffic flowing through the firewalls. Can anyone confirm what sort of traffic senderbase traffic is? Is it dns/html? I cant see a thing getting blocked for the ironport but there must be something getting stopped on the way out or in.

Email traffic appears to be working fine so thats not affected, its just the extra load and spam we are getting in that is the problem.

The ironports are running the latest software version 8.5.6-074.

Thanks

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Recent upgrade?  You can try

Recent upgrade?  You can try to run repengupdate force from the CLI.

Check senderbasestatus and repengstatus to see what is running... then run the repengupdate force.  You can tail updater_logs and watch the updating in progress, and see when it finishes...

After, recheck senderbasestatus.  If you can telnet to phonehome.senderbase.org 443, you should be getting updates...

Should be seeing simlar to:

myesa.local> repengstatus

  Component                   Last Update                     Version
  Reputation Engine           04 Aug 2014 16:05 (GMT +00:00)  1.2.0-079
  Reputation Engine Tools     04 Aug 2014 16:05 (GMT +00:00)  1.2.0-079


myesa.local> senderbasestatus

SenderBase Host Status
Status as of:                    Mon Aug 11 11:57:48 2014 GMT
Host success/fail:               success

SBRS Status
Status as of:                    Mon Aug 11 11:57:50 2014 GMT
Host success/fail:               success

SenderBase Network Participation Status
Time of last SenderBase upload:  Tue Aug 19 12:28:33 2014 GMT

myesa.local> repengupdate force

Reputation Engine updates:
Forcing update of Reputation Engine

myesa.local> tail updater_logs

(*you'll want to watch the logs and assure you see similar...)

Tue Aug 19 12:41:20 2014 Info: repeng successfully downloaded file "repeng/1.2/repeng/default/1392120079"
Tue Aug 19 12:41:20 2014 Info: repeng started applying files
Tue Aug 19 12:41:22 2014 Info: repeng cleaning up base dir [bindir]
Tue Aug 19 12:41:22 2014 Info: repeng verifying applied files
Tue Aug 19 12:41:22 2014 Info: repeng updating the client manifest
Tue Aug 19 12:41:22 2014 Info: repeng update completed
Tue Aug 19 12:41:22 2014 Info: repeng waiting for new updates

 

With success over to phonehome.senderbase.org...

myesa.local> telnet phonehome.senderbase.org 443

Trying 208.90.58.115...
Connected to phonehome.senderbase.org.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

1 REPLY
Cisco Employee

Recent upgrade?  You can try

Recent upgrade?  You can try to run repengupdate force from the CLI.

Check senderbasestatus and repengstatus to see what is running... then run the repengupdate force.  You can tail updater_logs and watch the updating in progress, and see when it finishes...

After, recheck senderbasestatus.  If you can telnet to phonehome.senderbase.org 443, you should be getting updates...

Should be seeing simlar to:

myesa.local> repengstatus

  Component                   Last Update                     Version
  Reputation Engine           04 Aug 2014 16:05 (GMT +00:00)  1.2.0-079
  Reputation Engine Tools     04 Aug 2014 16:05 (GMT +00:00)  1.2.0-079


myesa.local> senderbasestatus

SenderBase Host Status
Status as of:                    Mon Aug 11 11:57:48 2014 GMT
Host success/fail:               success

SBRS Status
Status as of:                    Mon Aug 11 11:57:50 2014 GMT
Host success/fail:               success

SenderBase Network Participation Status
Time of last SenderBase upload:  Tue Aug 19 12:28:33 2014 GMT

myesa.local> repengupdate force

Reputation Engine updates:
Forcing update of Reputation Engine

myesa.local> tail updater_logs

(*you'll want to watch the logs and assure you see similar...)

Tue Aug 19 12:41:20 2014 Info: repeng successfully downloaded file "repeng/1.2/repeng/default/1392120079"
Tue Aug 19 12:41:20 2014 Info: repeng started applying files
Tue Aug 19 12:41:22 2014 Info: repeng cleaning up base dir [bindir]
Tue Aug 19 12:41:22 2014 Info: repeng verifying applied files
Tue Aug 19 12:41:22 2014 Info: repeng updating the client manifest
Tue Aug 19 12:41:22 2014 Info: repeng update completed
Tue Aug 19 12:41:22 2014 Info: repeng waiting for new updates

 

With success over to phonehome.senderbase.org...

myesa.local> telnet phonehome.senderbase.org 443

Trying 208.90.58.115...
Connected to phonehome.senderbase.org.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

1182
Views
10
Helpful
1
Replies
CreatePlease to create content