Showing results for 
Show  only  | Search instead for 
Did you mean: 

Move clients not able to connect to secondary SVM server

I am running MOVE multi-platform version on a couple of SVM servers. The clients are configured by an ePO policy to connect to both the SVM servers. I have found that updating ENS on the SVM server causes the clients to become unresponsive. Restarting the server would allow the clients to reconnect. Are the clients able to use multiple SVM servers if one become unresponsive for some reason?
3 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Move clients not able to connect to secondary SVM server

Clients will only use a single SVM for scan reputation lookup`s. If that SVM becomes unavailable then the client will failover to then use the secondary, assuming you have configured primary/secondary in your policy.

If you are using an SVM-MGR then a client finding its allocated SVM has stopped communicating will query the SVM-MGR for a new scan lease to be allocated. Deploying, and specifying  an SVM-MGR in your MOVE policy would be the preferred option for client - SVM allocation in anything other than small environments, as it automates the task of allocating which SVM a client will use.

Former Member
Not applicable
Report Inappropriate Content
Message 3 of 4

Re: Move clients not able to connect to secondary SVM server

Hello @ctcc-dave ,

Thank you for your query.

The assignment method being used was/is only meant for fail-over. If you would like to divide the amount of Clients among both available scan servers, then you must assign the primary scan server to the first group of Clients, and then using an additional policy, assign the primary (second server) to the second group of Clients. In doing so, you will not have fail-over capability, unless you decide to create two additional SVM's, and then designate each one as a secondary scan server. This policy setting is not intended to be used for load balancing, but you can achieve load balancing by using multiple policies, each with their own specifically designated primary scan server.

Level 7
Report Inappropriate Content
Message 4 of 4

Re: Move clients not able to connect to secondary SVM server

I found documentation "Assign the SVM manually without SVM Manager" and it looks like you can use two SVM's without a manager and load balance between the two.

Can you confirm?

1). Log on to McAfee ePO as an administrator.
2). Click Menu → Policy → Policy Catalog, select MOVE AntiVirus 4.7.0 from the Product drop-down list, then select Options from the Category drop-down list.
3). Click New Policy or click the name of an existing policy to edit it.
4). Type a name for the new policy (for example, SVM Assignment Policy), then click OK.
5). Under SVM Assignment on the policy settings page, configure these options, then click Save.
5a). Select Assign SVM manually and configure the SVMs details:
5b). Enter IP Address or FQDN (domain name) of SVM-1, and the SVM-1 Port. Default is 9053.
NOTE: McAfee MOVE AntiVirus Multi-Platform supports Fully Qualified DNS names, which allow for DNS Round-Robin Load Balancing. This type of load balancing distributes client requests across multiple servers.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community