How to use Symantec Enterprise Security Manager on a computer that has two network cards

Article:TECH196881  |  Created: 2012-09-18  |  Updated: 2012-10-12  |  Article URL http://www.symantec.com/docs/TECH196881
Article Type
Technical Solution


Environment

Issue



This document explains how to configure a computer that has multiple network cards to work with the Symantec Enterprise Security Manager manager or agent.


Environment



Windows Server 2003

ESM 10

CCS  11

Customer has an ESM Agent or Manager that is multihomed which is causing communication issues


Solution



You can run the manager or agent on a computer that has two or more network cards by configuring the operating system to run all ESM traffic through a single network card. Note that ESM does not have settings that will accomplish this.

Use the operating system's routing table to specify which network traffic goes though which network card.

ESM Agent
For instance, the routing table on a computer that runs the ESM agent and has two or more network cards will appear similar to the following. Use one routing entry for each manager to which this agent is registered.

===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 192.17.12.1 192.17.14.144
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.17.12.0 255.255.252.0 192.17.14.144 192.17.14.144
192.17.14.144 255.255.255.255 127.0.0.1 127.0.0.1
192.17.255.255 255.255.255.255 192.17.14.144 192.17.14.144
224.0.0.0 224.0.0.0 192.17.14.144 192.17.14.144
255.255.255.255 255.255.255.255 192.17.14.144 192.17.14.144
<IP of the ESM Manager> <Current netmask> <current gateway> <Interface ESM should use>
Default Gateway: 192.17.12.1
===========================================================================



ESM Manager
The routing table on a computer that runs the ESM manager and has two or more network cards will appear similar to the following. Use one routing entry for each ESM agent that is registered to that manager.

===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 192.17.12.1 192.17.14.144
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.17.12.0 255.255.252.0 192.17.14.144 192.17.14.144
192.17.14.144 255.255.255.255 127.0.0.1 127.0.0.1
192.17.255.255 255.255.255.255 192.17.14.144 192.17.14.144
224.0.0.0 224.0.0.0 192.17.14.144 192.17.14.144
255.255.255.255 255.255.255.255 192.17.14.144 192.17.14.144
<IP of the ESM Agent> <Current netmask> <current gateway> <Interface ESM should use>
<IP of the ESM Agent> <Current netmask> <current gateway> <Interface ESM should use>
<IP of the ESM Agent> <Current netmask> <current gateway> <Interface ESM should use>
<IP of the ESM Agent> <Current netmask> <current gateway> <Interface ESM should use>
Default Gateway: 192.17.12.1
===========================================================================
 




Article URL http://www.symantec.com/docs/TECH196881


Terms of use for this information are found in Legal Notices