0% found this document useful (0 votes)
68 views

NXLL32 GLBP Gateway Load Balancing ProtocolLAB

1. The document describes configuring GLBP (Gateway Load Balancing Protocol) on routers MLS1-MLS4. 2. EIGRP is configured to allow routing between routers, and PAT is configured on router R1 to allow traffic from multiple private networks to use a single public IP address. 3. GLBP is configured on the MLS routers with authentication, and the priorities are set so that MLS2 will be the active virtual gateway while the others serve as active virtual forwarders to load balance traffic.

Uploaded by

Abu Fadilah
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
68 views

NXLL32 GLBP Gateway Load Balancing ProtocolLAB

1. The document describes configuring GLBP (Gateway Load Balancing Protocol) on routers MLS1-MLS4. 2. EIGRP is configured to allow routing between routers, and PAT is configured on router R1 to allow traffic from multiple private networks to use a single public IP address. 3. GLBP is configured on the MLS routers with authentication, and the priorities are set so that MLS2 will be the active virtual gateway while the others serve as active virtual forwarders to load balance traffic.

Uploaded by

Abu Fadilah
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Lab 32: GLBP (Gateway Load Balancing Protocol)

Task

Figure 1 Topology

1. Configure IP Address as per given in topology.


2. Configure Eigrp as per given in topology.
3. Configure PAT on R1.
4. Configure GLBP on MLS1, MLS2, MLS3 & MLS4.
5. Make sure MLS2 is become AVG (Active Virtual Gateway) and rest of all become AVF (Active
Virtual Forwarders)
6. Use GLBP authentication "N#!W@xL@B".
7. Make sure All PC's are able to ping www.netwaxlab.com and blog.eincop.com
Lab 32: GLBP (Gateway Load Balancing Protocol)

Solution
Task 2: Configure Eigrp as per given in topology.

R1

router eigrp 100


redistribute static
network 192.168.1.0
no auto-summary
exit

MLS1 to MLS4

router eigrp 100


network 0.0.0.0
no auto-summary
exit

Task 3: Configure PAT on R1.

R1

ip route 0.0.0.0 0.0.0.0 172.54.29.1

ip access-list extended NAT


permit ip 192.168.1.0 0.0.0.255 any
permit ip 192.168.200.0 0.0.0.255 any
exit

int f0/0
ip nat outside
exit

int f0/1
ip nat inside
exit

ip nat inside source list NAT interface FastEthernet0/0 overload


Lab 32: GLBP (Gateway Load Balancing Protocol)

Task 4: Configure GLBP on MLS1, MLS2, MLS3 & MLS4.

MLS1 to MLS4

int f1/2
glbp 1 ip 192.168.200.254
glbp 1 preempt
exit

Task 5: Make sure MLS2 is become AVG (Active Virtual Gateway) and rest of all become AVF
(Active Virtual Forwarders)

MLS1

int f1/2
glbp 1 priority 190
exit

MLS2

int f1/2
glbp 1 priority 200
exit

MLS3

int f1/2
glbp 1 priority 191
exit

MLS4

int f1/2
glbp 1 priority 192
exit

Task 6: Use GLBP authentication "N#!W@xL@B".

MLS1 to MLS4

int f1/2
glbp 1 authentication md5 key-string N#!W@xL@B
exit
Lab 32: GLBP (Gateway Load Balancing Protocol)

Task 7: Make sure All PC's are able to ping www.netwaxlab.com and blog.eincop.com

(Note: Provide Glbp Virtual IP address 192.168.200.254 to all the Pc's Gateway so that they can
communicate with MLS.)

You might also like