Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Spreading activity among three NICs

Created: 24 Sep 2012 | 11 comments

Hello all,

New to the forum and this product (BE 2012).  I am in the process of setting up multiple backup jobs.  My server has four NIC's.  I have setup one as an external IP for me to access the server remotely.  The other three NIC's are in my DMZ (*.22,*.23,*.24).  I was hoping that the Symantec software would pick an available NIC and run with it.  Instead all my jobs are running through the *.22 which I am assuming is causing a bottleneck and performance issues because my jobs are really slow.

Have tried going into the agent on the remote server and changing the IP address from *.22 to *.23. I ran trust on the BE Server. I edited the job for that server to use the *.23 NIC and the job immediately fails with a comm error.

I tried to uninstall and re-install the agent and point to *.23 and it still fails saying it can not connect.

I can ping from the remote server *.22, *.23 and *.24.  Have to assume I need to do something in Symantec. 

The software appears to want to be flexible about using the NIC's.  Jobs will allow me to point to any one of the three, it just won't connect to anything other than *.22.  Open to any ideas or suggestions.

Thx,

Douglas

Comments 11 CommentsJump to latest comment

ub40's picture

Hi, Douglas

I think, that the BE can't use any NIC, since he haven't information about routes through additional NIC.
By default main rote build through one NIC.
You must create different rotes for all NIC, or if NIC 22-24 have address in same network segment, combine this NIC in network team and create any routes for network team.

Reards,
UB

AKSM-IT's picture

UB40,

Are you talking about banking the NIC's on the server like you would do for failover?  Allowing symantec to continue to point to 22 but then allow the server to move traffic among the NICs as needed?

Or, are you suggesting something else?

Thx,

Douglas

Jaydeep S's picture

You could also go the individual job properties and maually set a perticular job to use a perticular network.

AKSM-IT's picture

Jaydeep,

Tried this and I get a communiction error.  Will only work if I leave it at default to pick nic or manually set to *.22

Douglas

Jaydeep S's picture

Is each of the that network card connected to a different network. i.e do you have multiple subnets available at both ends, Media server and Remote Servers. If not then what ub40 mentioned is the only way out as in use Nic teaming.

AKSM-IT's picture

Jaydeep,

One NIC is on say 111.111.1.9 (outside)

The other three are on 111.111.2.22, 2.23, 2.24 (DMZ)

subnets 255.255.255.0

Guess I am trying Nic Teaming.

Thx

AKSM-IT's picture

Well I tried team Nic's and I have a different issue that I hope you can help me with.

I took all three of my 111.111.2.22, 23, & 24 addresses and put them in one team using HP's NIC Utility for my server (Proliant DL380 G6).

In order for 22 to work originally (prior to teaming), I had to add routing as such:

Route Add 222.222.222.222 mask 255.255.255.0 111.111.1.1 - p

for each of my remote servers.

Where 222.222.222.222 is the remote IP of the server I wished to backup and 111.111.1.1 is the DMZ Gateway address.

When the NIC's stayed apart, I could ping and symantec could backup my remote servers.  When I teamed them, it appears to have broken my routing table because I can no longer ping or connect to the remote servers.  The team got an IP address of 169.254.*.  The software the teamed the NIC's does appear to allow me to change this IP.  When I dissolve the team, I am able to ping and connect to the servers again.

Ideas for how to make this work?

pkh's picture

BE will not pick any interface to run.  You can choose a specific interface, but BE will not load balance the interfaces, so to speak.

ub40's picture

Hi, Douglas.

Sow route print for IPV4 on you server

Regards,

UB

 

AKSM-IT's picture

UB40,

See attached Route Print.

Got approval from IT Director to post internal addresses so now I can share better details.

192.168.1.* is internal addressing through our firewall

192.168.11.* is within our DMZ

All other addresses are company locations we aquired that have VPN connects to us such as 192.168.107 and 172.16.0.  Each of the persistent addresses are the locations I am trying to backup and use the teaming nics.

Thx for your assistance,

Douglas

AttachmentSize
RoutePrint.pdf 119.16 KB
ub40's picture

Douglas,

if I understand correctly - interface 192.168.1.18 is main interface on server (domain network access, DNS, WINS) ?

NICs with DMZ addresses are intended to access backup targets and netwok team address has the form 192.168.11.x ?

In this case yours first record must has the form

Network Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 192.168.1.2 192.168.1.18

All other route to 0.0.0.0 must delete

For DMZ team route record must has form

Network Destination Netmask Gateway Interface
192.168.11.0 255.255.255.0 192.168.11.2 192.168.11.x

All other route through DMZ team must written similarly

If DMZ does not have DNS server you can add backup targets name and ip address to host file.

On my server in job properties I select "IPv4" Protocol and "Use any available network interface" value on the Network and Security tabs

Regards,

UB