davidarndt
Technical User
Superstack 3, 4900, Server with two GBEthernet Server NICs (3c996B-T). The server is running Windows 2000 Server and will act as a storage appliance.
I'd like to aggregate two ports on the SuperStack and team the two NICs as a LoadBalanced team connected to the aggregated ports.
Four application servers (WinNT/Win2000) will be connected to this "inside" LAN. The main server also has a 100mbs NIC connected to an "outside" LAN with client workstations on it.
I want to hand out private IP addresses from a DHCP service on the storage appliance server to the inside LAN servers. The outside LAN NIC will get its IP address from an outside DHCP server.
I have two questions:
1. Will the port aggregation/teaming scheme work?
2. How do I deal with name resolution with the inside LAN servers? If I point them to the outside LAN DNS server, they'll see the outside LAN IP address for the storage appliance (or both, which might be worse yet since I'd get round-robin resolution...).
Thanks!
David
I'd like to aggregate two ports on the SuperStack and team the two NICs as a LoadBalanced team connected to the aggregated ports.
Four application servers (WinNT/Win2000) will be connected to this "inside" LAN. The main server also has a 100mbs NIC connected to an "outside" LAN with client workstations on it.
I want to hand out private IP addresses from a DHCP service on the storage appliance server to the inside LAN servers. The outside LAN NIC will get its IP address from an outside DHCP server.
I have two questions:
1. Will the port aggregation/teaming scheme work?
2. How do I deal with name resolution with the inside LAN servers? If I point them to the outside LAN DNS server, they'll see the outside LAN IP address for the storage appliance (or both, which might be worse yet since I'd get round-robin resolution...).
Thanks!
David