NIC configuration for NLB and fail over cluster.

-

 

what nic configuration should use iis nlb , sql fail on cluster? target avoid single point of failure connection including switches.

scenario:

2 servers in nlb clustering (domain member)

2 servers in sql , file fail on clustering (both domain controllers)

webpage iis server stored on fail on cluster (i don’t want use dfsr replication) using \\fileclustername\folder

iis servers connect sql database cluster ip.

and problem how should set nic addressing?

idea:

nlb cluster

 

nlb node 1

public1 & public2 = publicnictem

ip 192.168.100.50

mask: 255.255.255.0

gateway: 192.168.100.254

dns: n/a

 

heartbeat1

ip 10.10.100.10

mask: 255.255.255.0

gateway: n/a

dns: /na

               

heartbeat2

ip 10.10.110.10

mask: 255.255.255.0

gateway: n/a

dns: /na

 

private1 & private2 = privatenicteam

ip 172.16.100.50

mask: 255.255.255.0

gateay: n/a

dns: 172.16.100.10

          172.16.100.20

 

nlb node 2

public1 & public2 = publicnictem

ip 192.168.100.60

mask: 255.255.255.0

gateway: 192.168.100.254

dns: n/a

 

heartbeat1

ip 10.10.100.20

mask: 255.255.255.0

gateway: n/a

dns: /na

               

heartbeat2

ip 10.10.110.20

mask: 255.255.255.0

gateway: n/a

dns: /na

 

private1 & private2 = privatenicteam

ip 172.16.100.60

mask: 255.255.255.0

gateay: n/a

dns: 172.16.100.10

          172.16.100.20

 

 

public nlb cluster ip (on 2 publicnicteam)

192.168.100.100

mask: 255.255.255.0

 

fail on cluster

 

sql f/o node 1

private1 & private2 = privatenicteam

ip 172.16.100.10

mask: 255.255.255.0

gateay: n/a

dns: 172.16.100.10

 

heartbeat1

ip 10.10.120.10

mask: 255.255.255.0

gateway: n/a

dns: /na

               

heartbeat2

ip 10.10.130.10

mask: 255.255.255.0

gateway: n/a

dns: /na

 

sql f/o node 2

public1 & public2 = publicnictem

ip 172.16.100.20

mask: 255.255.255.0

gateay: n/a

dns: 172.16.100.10

 

heartbeat1

ip 10.10.120.20

mask: 255.255.255.0

gateway: n/a

dns: /na

               

heartbeat2

ip 10.10.130.20

mask: 255.255.255.0

gateway: n/a

dns: /na

 

public sql f/o cluster ip (on 2 publicnicteam)

172.16.100.50

mask: 255.255.255.0

 

does make sense?

 hi,

this work, in opinion whole architecture liitle bit "overpowered". how many 9's have achieve ?

bye.
thorstenwujek


Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more