Re: CISCO GLBP PROTOCOL

grupporete · ‎01-08-2006

I have implemented

Cisco Glbp protocol in a lan where there was HSRP.

Now the situation is that the balancing is only on the LAN side (60%-40%)but the imput side ( WAN- Serial Interface)is still unbalanced.

This is normal or can I have a balancing also in the input zone?

Thanks

Alberto

Richard Burts · ‎01-08-2006

Alberto

I believe that you are seeing normal behavior. Protocols like GLBP are effective with sending traffic on the LAN side but have little ability to control how traffic is sent to you over the WAN links. Control of how traffic is sent to you over the WAN links is the responsibility of the remote router that is sending the traffic over the WAN.

HTH

Rick

HTH

Rick

grupporete · ‎01-09-2006

ROUTER1#sh int fa0/0

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0007.0e83.6860 (bia 0007.0e83.6860)

Description: LINK verso xxxx fa5/24

Internet address is x.x.x.x/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 2/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 10Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/569/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 17000 bits/sec, 8 packets/sec

5 minute output rate 109000 bits/sec, 9 packets/sec

59133323 packets input, 3063440677 bytes

Received 2210177 broadcasts, 0 runts, 0 giants, 0 throttles

34 input errors, 0 CRC, 0 frame, 34 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

40328405 packets output, 1685116135 bytes, 0 underruns

0 output errors, 0 collisions, 16 interface resets

*****************************************************

ROUTER2#sh int fa0/0

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0003.6b43.4820 (bia 0003.6b43.4820)

Description: LINK verso fa4/24

Internet address is x.x.x.x/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 4/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 10Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/1367/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 7000 bits/sec, 6 packets/sec

5 minute output rate 176000 bits/sec, 23 packets/sec

38309659 packets input, 3859162388 bytes

Received 2154996 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

30695886 packets output, 3555680397 bytes, 0 underruns

0 output errors, 0 collisions, 9 interface resets

0 babbles, 0 late collision, 0 deferred

***********************************************

This is the situation: The first is priority 150

The second is priority 100

The question is:

By checking the input and output packet of the both rouetr's FAstethernet interfaces, Can I say that GLBP are working fine?

Thanks for your reply

johansens · ‎01-08-2006

Hi there Alberto,

This is normal. The GLBP protocol is a LAN-side protocol meant to enable load-balancing for hosts on a LAN which doesn't have a 'clue' about redundant paths.

To enable load balancing on the input of the wan-side, you'll have to either run a routing-protocol or have the sending side (the other sides) manually set static routes which enable the load balancing.

See this link for more information:

"IP Routing - How Does Load Balancing Work?"

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094820.shtml

Did it help? If so, please rate it.

grupporete · ‎01-09-2006

ROUTER1#sh int fa0/0

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0007.0e83.6860 (bia 0007.0e83.6860)

Description: LINK verso xxxx fa5/24

Internet address is x.x.x.x/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 2/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 10Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/569/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 17000 bits/sec, 8 packets/sec

5 minute output rate 109000 bits/sec, 9 packets/sec

59133323 packets input, 3063440677 bytes

Received 2210177 broadcasts, 0 runts, 0 giants, 0 throttles

34 input errors, 0 CRC, 0 frame, 34 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

40328405 packets output, 1685116135 bytes, 0 underruns

0 output errors, 0 collisions, 16 interface resets

*****************************************************

ROUTER2#sh int fa0/0

FastEthernet0/0 is up, line protocol is up

Hardware is AmdFE, address is 0003.6b43.4820 (bia 0003.6b43.4820)

Description: LINK verso fa4/24

Internet address is x.x.x.x/24

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 4/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 10Mb/s, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/1367/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 7000 bits/sec, 6 packets/sec

5 minute output rate 176000 bits/sec, 23 packets/sec

38309659 packets input, 3859162388 bytes

Received 2154996 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog

0 input packets with dribble condition detected

30695886 packets output, 3555680397 bytes, 0 underruns

0 output errors, 0 collisions, 9 interface resets

0 babbles, 0 late collision, 0 deferred

***********************************************

This is the situation: The first is priority 150

The second is priority 100

The question is:

By checking the input and output packet of the both rouetr's FAstethernet interfaces, Can I say that GLBP are working fine?

Thanks for your reply

Richard Burts · ‎01-09-2006

Alberto

Based on what you have posted I believe there is not any sign of a problem. You have very close to a 60/40 split of traffic both inbound and outbound on these interfaces. It looks to me like GLBP is working as expected.

HTH

Rick

HTH

Rick

grupporete · ‎01-09-2006

Rick,

last question:

Did you think GLBP has to balance in inbound or in outbound.

That' s becasue in other situation We only the outbound traffic balanced.

Many thanks