dual nics web server network
Today: IIS/SSL to SqlServer. Of course, many problems exist from performance, redundancy, security.
Tomorrow: Cisco/SSL to Apache/Linux to SqlServer/Oracle and File server and LDAP server
My design was to place dual NICs in the web servers. Have the Cisco handle all SSL ( using an add-on module ) and load balancing/failover pointing to ONE NIC on each Webby.
Have the Second NIC point to the backend network for access to DB and other backend servers.
I'm getting push back from the implementor saying this configuration is weird and unnecessary. He wants to go with one NIC and configure everything at the new switch.
While points of bandwidth can be pointed in my favor I'd like to also believe security is in my choice of layout as well.
It's coming down to a problem I'm having configuring the dual NICs on the Linux box.
PROBLEM: The external ( switch side ) NIC is class C with a 10.10 network. The internal ( Db side ) NIC is class B with a 172.16 network. The switch will not get responses back.
If I change the internal to a 192.168 network, then it works from the switch but I lose connectivity to the backend servers running 172.16
I'm not terribly advanced with complex network design. Any insight would be appreciated.
Len
