- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- Isolated Backup Network via NIC Teaming
Networking
1822497
Members
2441
Online
109642
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2009 07:11 PM
10-15-2009 07:11 PM
Isolated Backup Network via NIC Teaming
I am setting up an isolated backup network that I would like to keep production traffic off and visa versa.
The issue I am having is that if I enable the "Backup Network" Team, ip resolves eventually go to this network team which is isolated to its self via Vlan 110.
I would like to configure the Teams based on priority or exclusion. Where Team Nic01 is priority one, Team Nic02 is priority two, and Backup Network is only used by the backup software that sees only what server is on that Vlan.
Currently the Teams are configured with TLB and Round Robin (packet order not guaranteed)
I thank you in advance for any suggestions.
Network Team Nic01 172.22.30.xx, Vlan 10
Network Team Nic02 192.1.1.xx, Vlan 11
Backup Network 172.22.130.xx, Vlan 110
Vlan 10 sees Vlan 11, Vlan 11 sees Vlan 10 but Vlan 110 does not see either Vlan 10 or 11
The issue I am having is that if I enable the "Backup Network" Team, ip resolves eventually go to this network team which is isolated to its self via Vlan 110.
I would like to configure the Teams based on priority or exclusion. Where Team Nic01 is priority one, Team Nic02 is priority two, and Backup Network is only used by the backup software that sees only what server is on that Vlan.
Currently the Teams are configured with TLB and Round Robin (packet order not guaranteed)
I thank you in advance for any suggestions.
Network Team Nic01 172.22.30.xx, Vlan 10
Network Team Nic02 192.1.1.xx, Vlan 11
Backup Network 172.22.130.xx, Vlan 110
Vlan 10 sees Vlan 11, Vlan 11 sees Vlan 10 but Vlan 110 does not see either Vlan 10 or 11
- Tags:
- NIC
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2009 04:52 PM
11-16-2009 04:52 PM
Re: Isolated Backup Network via NIC Teaming
Im not sure if I understand your issue, but you can add static routes on windows, it will allow to send traffic to an specific gateway.
For example, if you were on VLAN10 and you had a gateway on 172.22.30.1 configured to access the 10.10.10.0/24 network, you can use a route add statement like this:
route ADD 10.10.10.0 MASK 255.255.255.0 172.22.30.1
Then the traffic for that network will go to that gateway instead of the backup network.
For example, if you were on VLAN10 and you had a gateway on 172.22.30.1 configured to access the 10.10.10.0/24 network, you can use a route add statement like this:
route ADD 10.10.10.0 MASK 255.255.255.0 172.22.30.1
Then the traffic for that network will go to that gateway instead of the backup network.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP