Configuring the SLB Topology Example
SLB Configuration Guidelines and Prerequisites
Configuring the SLB-L2 Topology Example
SLB-L2 Configuration Guidelines and Prerequisites
Conditions for a Member Participating in Load Distribution
Set the Traffic Distribution Policy
Restore the Default Traffic Distribution Policy
Set the Health-Monitor Parameters
View the Traffic Distribution Policy
Restore the Default Traffic Distribution Policy
Restore the Default Failover Method
Creating Example SLB Configurations
Creating a Basic SLB Configuration
Enable the Switch Ports (Basic SLB)
Save the Current Configuration (Basic SLB)
Creating a Separate VLAN SLB Configuration
Separate VLAN SLB Configuration
Configuration With Separate VLANs Steps
Set Up the Switch (Separate VLAN SLB)
Set Up the Client (Separate VLAN SLB)
Set Up the Server (Separate VLAN SLB)
Enable the Switch Ports (Separate VLAN SLB)
Save the Current Configuration (Separate VLAN SLB)
Creating a Multiple SLB Group Configuration
Multiple-SLB-Group Configuration
Configuration With Multiple SLB Groups Steps
Set Up the Client (Multiple SLB Group)
Set Up the Servers in SLB Group 1
Set Up the Servers in SLB Group 2
Enable the Switch Ports (Multiple SLB Group)
Save the Current Configuration (Multiple SLB Group)
Restart the Server Following Failure
Creating SLB-L2 Configuration Examples
Bump-In-The-Wire Configuration
Creating a Single-Switch Configuration
Basic Single-Switch Configuration
Create a Single-Switch Configuration
Creating a Dual-Switch Configuration
Create a Dual-Switch Configuration
In SLB, LBGs include server members identified by level-3 protocol (IP) addresses. Server members can be physical servers (server blades or rackmounted servers) or VMs with IP addresses assigned. Technically, server members in an LBG are multiple next hops of an ECMP route. Each LBG is identified by a VIP address that is used to represent the IP address of the virtual server. From the client network, the virtual server is highly available with dynamically reconfigurable resources. Load distribution is performed using the routing hash function of the switch. Load distribution policies are based on the contents of the L3/4 packet header. Failover is supported at the server member's level. A failed member within an LBG is replaced by another server member residing within the same LBG. A health check is performed by the switch using an ICMP ping.