Shulou(Shulou.com)06/02 Report--

This content is in Chapter 6 of Windows Server 2012 Network Management and Rack Station, and a simple record is made for this chapter.

Concept Record:

1. Architecture of Web Farm: Each node (firewall, Load Balancer device, WEB server, database server) has more than one, so as to provide Load Balancer function. Since Windows 2012 already includes Network Load Balancer (NLB), you can cancel Load Balancer device (F5, Deep Trust AD) and directly use Windows NLB to provide Load Balancer function.

2. Web page storage location: Each Web server must store the same web page content, which can be stored in SAN, NAS, file sharing server

3. Windows NLB overview: Fixed IP address, concept of clustered IP address, heartbeat listening to other servers, convergence program to build clusters, dependencies of Load Balancer (the way Load Balancer works, so to speak, depending on IP or port or something)

4. Windows operation mode: unicast, multicast, IGMP multicast, mainly distinguish between these ways MAC address difference, what problems will exist in the switch (such as flooding problem, MAC address learning problem)

Web Farm vs. NLB Instance: The test environment is as follows:

Configuration steps:

1. A configuration file server is used for establishing different shared folders to store web page files and website shared configuration files respectively, establishing users and endowing them with permissions.

2. WEB1 Settings: Copy the web page to the shared folder, assign the website home directory to the corresponding shared folder, export the shared configuration (shared configuration stores some configuration files of the WEB server) to the corresponding shared folder, and assign the path of the shared configuration to the corresponding shared folder.

3. WEB2 Settings: Specify the home directory of the website to the corresponding shared folder, and specify the path of the shared configuration to the corresponding shared folder.

4. Establish NLB: Install network load features, establish clusters (add hosts within clusters, set cluster IP addresses, set cluster mode, set port rules, etc.)

Test: multicast and unicast modes

1. Multicast mode: The MAC address of the cluster in multicast mode is a multicast MAC address, and the servers in the cluster will retain the original unique MAC address, as shown in the following figure:

In multicast mode, there will be switch flooding problem, because the source MAC of the message sent by the cluster host is not the cluster MAC address, so the switch port cannot learn the cluster MAC address. When the client sends a message to the cluster MAC address, the switch will flood all ports. To solve this problem, you need to select IGMP multicast mode (the switch must support IGMP snooping).

2. Unicast mode: Unicast mode cluster MAC address is a unicast MAC address, the servers in the cluster will replace the original MAC address, as shown in the following figure:

Switch flooding also exists in unicast mode, which can be solved by selecting IGMP multicast mode (switches must support IGMP snooping) or VLAN. Cluster nodes are grouped into the same VLAN to limit traffic flooding.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.