Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Symantec client do not update from replication partner

Created: 03 Dec 2012 | 11 comments

I have a main symantec server (A) and a replication server (B). When server A is down, all clients fail over to server B. The problem I am having is that though server B is updating properly, clients which connect with the SEPM do not get updated. Thus if server A is down since 16 November, though all clients are connecting with server B; the definition will still be that of 15 November.

Can you please let me know what could cause this problem? Any solution will be most welcomed.

To have the client connect with the SEPM B I had to copy everything in folder C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent from the main server to the replication server.

Discussion Filed Under:

Comments 11 CommentsJump to latest comment

Gavinash's picture

Hi Manish,

I was doing some more test today and found out that on the secondary SEPM (replication partner), there is no Policy Serial Number (View clients>Details). The clients are connecting with the SEPM (green dot), but none of them is taking update from the replication partner.

Can you please help me out.

Thanks in advance

Arvind

 

Ashish-Sharma's picture

HI,

check under SEP client GUI --> Help & support --> Troubleshooting --> Check Server Name or IP or any other status.

Also provide log.liveupdate

 

Thanks In Advance

Ashish Sharma

 

 

Gavinash's picture

Dear Ashish,

When I check SEP client GUI --> Help & support --> Troubleshooting --> the IP address of the server is displayed, client has green dot i.e., communicating with replication partner SEPM.

I stopped service Symantec Endpoint Protection Manager on the main SEPM so that all clients will failover to the replication partner.

When I checked the log.liveupdate, there is no new entry since I stopped the SEPM.

For information the main SEPM is on windows 2003 and the replication partner is on windows 2008.

Is there a way for me to launch the liveupdate on the client so that it tries to update from the replication partner?

Arvind

pete_4u2002's picture

smc service restart will intitate the heartbeat and check for definition if available. can you post the sylink log from the client?

Gavinash's picture

Dear Pete,

Please find attached the sylink log.

Arvind

AttachmentSize
SyLink.xml 3.75 KB
Ashish-Sharma's picture

HI Gavinash,

Can you provide your sepm server live update setting ?

 

LiveUpdate and content troubleshooting for the Symantec Endpoint Protection Manager

 

Article:TECH105924  |  Created: 2008-01-16  |  Updated: 2012-03-30  |  Article URLhttp://www.symantec.com/docs/TECH105924

Symantec Endpoint Protection: LiveUpdate Troubleshooting Flowchart

 

Article:TECH95790  |  Created: 2009-01-26  |  Updated: 2012-03-30  |  Article URLhttp://www.symantec.com/docs/TECH95790

 

 

Thanks In Advance

Ashish Sharma

 

 

Gavinash's picture

Ashish,

Both main SEPM and replication partner have same live update setting i.e., Use the default management server.

I stopped the SEPM service on the main SEPM for the weekend and found that the client does not request any update from the replication partner. Last entries of log.liveupdate is when client was connected to the main SEPM.

LiveUpdate Settings policy.jpg
Ashish-Sharma's picture

hi,

kindly post the syslink.log.

You can wrongly paste the sylink.xml file.

 

Thanks In Advance

Ashish Sharma

 

 

Gavinash's picture

Hi,

Plz find sylink.log, replication partner IP is 172.20.4.57.

Thanks for your help!!

 

AttachmentSize
Sylink.zip 26.08 KB
Ambesh_444's picture

Hi,

Means your 1st priority server is down now and from replication server (2nd Priority) clients are not geting updated.

Please check in your SEPM console and let me know.

 

To configure failover and load balancing

1. In the Symantec Endpoint Protection Manager Console, click Policies.
2. In the View Policies pane, to the right of Policy Components, click the up arrow so that it becomes a down arrow, and then click Management Server Lists.
3. In the Tasks pane, click Add a Management Server List.
4. In the Management Server Lists dialog box, under Management Servers, click Add > New Priority three times.
5. Under Management Servers, click Priority 1.
6. Click Add > New Server.
7. In the Add Management Server dialog box, in the Server Address box, type the fully qualified domain name or IP address of a Symantec Endpoint
Protection Manager.

o    If you type an IP address, be sure that it is static, and that all clients can resolve the IP address.

8. Click OK.
9. Do one of the following:

o    To configure load balancing with the other server, click Priority 1.

o    To configure failover with the other server, click Priority 2.

10. Click Add > New Server.
11. In the Add Management Server dialog box, in the Server Address box, type the fully qualified domain name or IP address of a Symantec Endpoint
Protection Manager.

o    If you type an IP address, be sure that it is static, and that all clients can resolve it.

12. Click OK.
13. (Optional) To change the priority of a server, which changes the load balancing
or failover configuration, click a server, and then do one of the following:

o    Click Move up.

o    Click Move Down.

14. In the Management Server Lists dialog box, click OK.

To apply the Management Server List
1. In the right pane, under Management Server Lists, under Name, click on and highlight the Management Server List that you created.
2. In the lower-left Tasks pane, click Assign the list.
3. In the Apply Management Server List dialog box, check the groups to which to apply the list.
4. Click Assign.
5. In the Assign Management Server List dialog box, click Yes.

 

 

 

Thank& Regards,

Ambesh

"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."