Guest

Cisco IOS Software Releases 12.2 T

GLBP - Gateway Load Balancing Protocol

Table Of Contents

GLBP - Gateway Load Balancing Protocol

Contents

Prerequisites for Gateway Load Balancing Protocol

Information About Gateway Load Balancing Protocol

GLBP

GLBP Active Virtual Gateway

GLBP Virtual MAC Address Assignment

GLBP Virtual Gateway Redundancy

GLBP Virtual Forwarder Redundancy

GLBP Gateway Priority

GLBP Gateway Weighting and Tracking

GLBP Benefits

How to Configure Gateway Load Balancing Protocol

Customizing GLBP

GLBP Customizing Behavior

What to Do Next

Configuring GLBP Weighting Values and Object Tracking

GLBP Weighting Configuration Behavior

Enabling and Verifying GLBP

Prerequisites

Examples

Sample Output for the show glbp Command

Troubleshooting Gateway Load Balancing Protocol

Prerequisites

Configuration Examples for Gateway Load Balancing Protocol

Customizing GLBP Configuration Example

Configuring GLBP Weighting Example

Enabling GLBP Configuration Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

debug condition glbp

debug glbp errors

debug glbp events

debug glbp packets

debug glbp terse

glbp authentication

glbp forwarder preempt

glbp ip

glbp load-balancing

glbp preempt

glbp priority

glbp timers

glbp timers redirect

glbp weighting

glbp weighting track

show glbp

track

Glossary


GLBP - Gateway Load Balancing Protocol


Gateway Load Balancing Protocol (GLBP) protects data traffic from a failed router or circuit, like Hot Standby Router Protocol (HSRP) and Virtual Router Redundancy Protocol (VRRP), while allowing packet load sharing between a group of redundant routers.

Feature Specifications for the Gateway Load Balancing Protocol

Feature History
 
Release
Modification

12.2(14)S

This feature was introduced.

12.2(15)T

This feature was integrated into Cisco IOS Release 12.2(15)T

Supported Platforms

Cisco 1700 series, Cisco 2600 series, Cisco 3620, Cisco 3631, Cisco 3640, Cisco 3660, Cisco 3725, Cisco 3745, Cisco 7100 series, Cisco 7200 series, Cisco 7400 series, Cisco 7500 series


Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

Prerequisites for Gateway Load Balancing Protocol

Information About Gateway Load Balancing Protocol

How to Configure Gateway Load Balancing Protocol

Configuration Examples for Gateway Load Balancing Protocol

Additional References

Command Reference

Glossary

Prerequisites for Gateway Load Balancing Protocol

Before configuring the GLBP feature, ensure that the routers can support multiple MAC addresses on the physical interfaces. For each GLBP forwarder to be configured, an additional MAC address is used.

Information About Gateway Load Balancing Protocol

To configure GLBP, you need to understand the following concepts:

GLBP

GLBP Active Virtual Gateway

GLBP Virtual MAC Address Assignment

GLBP Virtual Gateway Redundancy

GLBP Virtual Forwarder Redundancy

GLBP Gateway Priority

GLBP Gateway Weighting and Tracking

GLBP Benefits

GLBP

The Gateway Load Balancing Protocol feature provides automatic router backup for IP hosts configured with a single default gateway on an IEEE 802.3 LAN. Multiple first hop routers on the LAN combine to offer a single virtual first hop IP router while sharing the IP packet forwarding load. Other routers on the LAN may act as redundant GLBP routers that will become active if any of the existing forwarding routers fail.

GLBP performs a similar, but not identical, function for the user as the HSRP and the VRRP. HSRP and VRRP protocols allow multiple routers to participate in a virtual router group configured with a virtual IP address. One member is elected to be the active router to forward packets sent to the virtual IP address for the group. The other routers in the group are redundant until the active router fails. These standby routers have unused bandwidth that the protocol is not using. Although multiple virtual router groups can be configured for the same set of routers, the hosts must be configured for different default gateways, which results in an extra administrative burden. GLBP provides load balancing over multiple routers (gateways) using a single virtual IP address and multiple virtual MAC addresses. Each host is configured with the same virtual IP address, and all routers in the virtual router group participate in forwarding packets. GLBP members communicate between each other through hello messages sent every 3 seconds to the multicast address 224.0.0.102, User Datagram Protocol (UDP) port 3222 (source and destination).

GLBP Active Virtual Gateway

Members of a GLBP group elect one gateway to be the active virtual gateway (AVG) for that group. Other group members provide backup for the AVG in the event that the AVG becomes unavailable. The AVG assigns a virtual MAC address to each member of the GLBP group. Each gateway assumes responsibility for forwarding packets sent to the virtual MAC address assigned to it by the AVG. These gateways are known as active virtual forwarders (AVFs) for their virtual MAC address.

The AVG is responsible for answering Address Resolution Protocol (ARP) requests for the virtual IP address. Load sharing is achieved by the AVG replying to the ARP requests with different virtual MAC addresses.

In Figure 1, Router A is the AVG for a GLBP group, and is responsible for the virtual IP address 10.21.8.10. Router A is also an AVF for the virtual MAC address 0007.b400.0101. Router B is a member of the same GLBP group and is designated as the AVF for the virtual MAC address 0007.b400.0102. Client 1 has a default gateway IP address of 10.21.8.10 and a gateway MAC address of 0007.b400.0101. Client 2 shares the same default gateway IP address but receives the gateway MAC address 0007.b400.0102 because Router B is sharing the traffic load with Router A.

Figure 1 GLBP Topology

If Router A becomes unavailable, Client 1 will not lose access to the WAN because Router B will assume responsibility for forwarding packets sent to the virtual MAC address of Router A, and for responding to packets sent to its own virtual MAC address. Router B will also assume the role of the AVG for the entire GLBP group. Communication for the GLBP members continues despite the failure of a router in the GLBP group.

GLBP Virtual MAC Address Assignment

A GLBP group allows up to four virtual MAC addresses per group. The AVG is responsible for assigning the virtual MAC addresses to each member of the group. Other group members request a virtual MAC address after they discover the AVG through hello messages. Gateways are assigned the next MAC address in sequence. A virtual forwarder that is assigned a virtual MAC address by the AVG is known as a primary virtual forwarder. Other members of the GLBP group learn the virtual MAC addresses from hello messages. A virtual forwarder that has learned the virtual MAC address is referred to as a secondary virtual forwarder.

GLBP Virtual Gateway Redundancy

GLBP operates virtual gateway redundancy in the same way as HSRP. One gateway is elected as the AVG, another gateway is elected as the standby virtual gateway, and the remaining gateways are placed in a listen state.

If an AVG fails, the standby virtual gateway will assume responsibility for the virtual IP address. A new standby virtual gateway is then elected from the gateways in the listen state.

GLBP Virtual Forwarder Redundancy

Virtual forwarder redundancy is similar to virtual gateway redundancy with an AVF. If the AVF fails, one of the secondary virtual forwarders in the listen state assumes responsibility for the virtual MAC address.

The new AVF is also a primary virtual forwarder for a different forwarder number. GLBP migrates hosts away from the old forwarder number using two timers that start as soon as the gateway changes to the active virtual forwarder state. GLBP uses the hello messages to communicate the current state of the timers.

The redirect time is the interval during which the AVG continues to redirect hosts to the old virtual forwarder MAC address. When the redirect time expires, the AVG stops redirecting hosts to the virtual forwarder, although the virtual forwarder will continue to forward packets that were sent to the old virtual forwarder MAC address.

The secondary holdtime is the interval during which the virtual forwarder is valid. When the secondary holdtime expires, the virtual forwarder is removed from all gateways in the GLBP group. The expired virtual forwarder number becomes eligible for reassignment by the AVG.

GLBP Gateway Priority

GLBP gateway priority determines the role that each GLBP gateway plays and what happens if the AVG fails.

Priority also determines if a GLBP router functions as a backup virtual gateway and the order of ascendancy to becoming an AVG if the current AVG fails. You can configure the priority of each backup virtual gateway with a value of 1 through 255 using the glbp priority command.

In Figure 1, if Router A, the AVG in a LAN topology, fails, an election process takes place to determine which backup virtual gateway should take over. In this example, Router B is the only other member in the group so it will automatically become the new AVG. If another router existed in the same GLBP group with a higher priority, then the router with the highest priority would be elected. If both routers have the same priority, the backup virtual gateway with the higher IP address would be elected to become the active virtual gateway.

By default, the GLBP gateway preemptive scheme is disabled. A backup virtual gateway can become the AVG only if the current AVG fails, regardless of the priorities assigned to the virtual gateways. You can enable the GLBP preemptive scheme using the glbp preempt command. Preemption allows a backup virtual gateway to become the AVG, if the backup virtual gateway is assigned a higher priority than the current AVG.

GLBP Gateway Weighting and Tracking

GLBP uses a weighting scheme to determine the forwarding capacity of each router in the GLBP group. The weighting assigned to a router in the GLBP group determines whether it will forward packets and, if so, the proportion of hosts in the LAN for which it will forward packets. Thresholds can be set to disable forwarding when the weighting falls below a certain value, and when it rises above another threshold, forwarding is automatically reenabled.

The GLBP group weighting can be automatically adjusted by tracking the state of an interface within the router. If a tracked interface goes down, the GLBP group weighting is reduced by a specified value. Different interfaces can be tracked to decrement the GLBP weighting by varying amounts.

GLBP Benefits

Load Sharing

You can configure GLBP in such a way that traffic from LAN clients can be shared by multiple routers, thereby sharing the traffic load more equitably among available routers.

Multiple Virtual Routers

GLBP supports up to 1024 virtual routers (GLBP groups) on each physical interface of a router, and up to 4 virtual forwarders per group.

Preemption

The redundancy scheme of GLBP enables you to preempt an active virtual gateway with a higher priority backup virtual gateway that has become available. Forwarder preemption works in a similar way, except that forwarder preemption uses weighting instead of priority and is enabled by default.

Authentication

You can use a simple text password authentication scheme between GLBP group members to detect configuration errors. A router within a GLBP group with a different authentication string than other routers will be ignored by other group members.

How to Configure Gateway Load Balancing Protocol

This section contains the following procedures:

Customizing GLBP (optional)

Configuring GLBP Weighting Values and Object Tracking (optional)

Enabling and Verifying GLBP (required)

Troubleshooting Gateway Load Balancing Protocol (optional)

Customizing GLBP

This task explains how to customize your GLBP configuration.

GLBP Customizing Behavior

Customizing the behavior of GLBP is optional. Be aware that as soon as you enable a GLBP group, that group is operating. It is possible that if you first enable a GLBP group before customizing GLBP, the router could take over control of the group and become the AVG before you have finished customizing the feature. Therefore, if you plan to customize GLBP, it is a good idea to do so before enabling GLBP.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ip address ip-address mask [secondary]

5. glbp group authentication text string

6. glbp group forwarder preempt [delay minimum seconds]

7. glbp group load-balancing [host-dependent | round-robin | weighted]

8. glbp group preempt [delay minimum seconds]

9. glbp group priority level

10. glbp group timers [msec] hellotime [msec] holdtime

11. glbp group timers redirect redirect timeout

12. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface type number

Example:

Router(config)# interface fastethernet 0/0

Specifies an interface type and number, and enters interface configuration mode.

Step 4 

ip address ip-address mask [secondary]

Example:

Router(config-if)# ip address 10.21.8.32 255.255.255.0

Specifies a primary or secondary IP address for an interface.

Refer to the "Configuring IP Addressing" chapter of the Release 12.2 Cisco IOS IP Configuration Guide for information on configuring IP addresses.

Step 5 

glbp group authentication text string

Example:

Router(config-if)# glbp 10 authentication text stringxyz

Authenticates GLBP packets received from other routers in the group.

If you configure authentication, all routers within the GLBP group must use the same authentication string.

Step 6 

glbp group forwarder preempt [delay minimum seconds]

Example:

Router(config-if)# glbp 10 forwarder preempt delay minimum 60

Configures the router to take over as AVF for a GLBP group if it has a higher priority than the current AVF.

This command is enabled by default with a delay of 30 seconds.

Use the optional delay and minimum keywords and the seconds argument to specify a minimum delay interval in seconds before preemption of the AVF takes place.

Step 7 

glbp group load-balancing [host-dependent | round-robin | weighted]

Example:

Router(config-if)# glbp 10 load-balancing host-dependent

Specifies the method of load balancing used by the GLBP AVG.

Step 8 

glbp group preempt [delay minimum seconds]

Example:

Router(config-if)# glbp 10 preempt delay minimum 60

Configures the router to take over as AVG for a GLBP group if it has a higher priority than the current AVG.

This command is disabled by default.

Use the optional delay and minimum keywords and the seconds argument to specify a minimum delay interval in seconds before preemption of the AVG takes place.

Step 9 

glbp group priority level

Example:

Router(config-if)# glbp 10 priority 254

Sets the priority level of the gateway within a GLBP group.

The default value is 100.

Step 10 

glbp group timers [msec] hellotime [msec] holdtime

Example:

Router(config-if)# glbp 10 timers 5 18

Configures the interval between successive hello packets sent by the AVG in a GLBP group.

The holdtime argument specifies the interval in seconds before the virtual gateway and virtual forwarder information in the hello packet is considered invalid.

The optional msec keyword specifies that the following argument will be expressed in milliseconds, instead of the default seconds.

Step 11 

glbp group timers redirect redirect timeout

Example:

Router(config-if)# glbp 10 timers redirect 600 7200

Configures the time interval during which the AVG continues to redirect clients to an AVF.

The timeout argument specifies the interval in seconds before a secondary virtual forwarder becomes invalid.

Step 12 

exit

Example:

Router(config-if)# exit

Exits interface configuration mode, and returns the router to global configuration mode.

What to Do Next

If you do not need to configure GLBP weighting values and object tracking, proceed to the "Enabling and Verifying GLBP" section.

Configuring GLBP Weighting Values and Object Tracking

This task explains how to configure GLBP weighting values and object tracking.

GLBP Weighting Configuration Behavior

GLBP weighting is used to determine whether a router can act as a virtual forwarder. Initial weighting values can be set and optional thresholds specified. Interface states can be tracked and a decrement value set to reduce the weighting value if the interface goes down. When the GLBP router weighting drops below a specified value, the router will no longer be an active virtual forwarder. When the weighting rises above a specified value, the router can resume its role as an active virtual forwarder.

SUMMARY STEPS

1. enable

2. configure terminal

3. track object-number interface type number {line-protocol | ip routing}

4. interface type number

5. glbp group weighting maximum [lower lower] [upper upper]

6. glbp group weighting track object-number [decrement value]

7. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

track object-number interface type number {line-protocol | ip routing}

Example:

Router(config)# track 2 interface POS 6/0 ip routing

Configures an interface to be tracked where changes in the state of the interface affect the weighting of a GLBP gateway.

This command configures the interface and corresponding object number to be used with the glbp weighting track command.

The line-protocol keyword tracks whether the interface is up. The ip routing keywords also check that IP routing is enabled on the interface, and an IP address is configured.

Step 4 

interface type number

Example:

Router(config)# interface fastethernet 0/0

Enters interface configuration mode.

Step 5 

glbp group weighting maximum [lower lower] [upper upper]

Example:

Router(config-if)# glbp 10 weighting 110 lower 95 upper 105

Specifies the initial weighting value, and the upper and lower thresholds, for a GLBP gateway.

Step 6 

glbp group weighting track object-number [decrement value]

Example:

Router(config-if)# glbp 10 weighting track 2 decrement 5

Specifies an object to be tracked that affects the weighting of a GLBP gateway.

The value argument specifies a reduction in the weighting of a GLBP gateway when a tracked object fails.

Step 7 

exit

Example:

Router(config-if)# exit

Exits interface configuration mode, and returns the router to global configuration mode.

Enabling and Verifying GLBP

This task explains how to enable GLBP on an interface and verify its configuration and operation. GLBP is designed to be easy to configure. Each gateway in a GLBP group must be configured with the same group number, and at least one gateway in the GLBP group must be configured with the virtual IP address to be used by the group. All other required parameters can be learned.

Prerequisites

If VLANs are in use on an interface, the GLBP group number must be different for each VLAN.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ip address ip-address mask [secondary]

5. glbp group ip [ip-address [secondary]]

6. exit

7. show glbp [interface-type interface-number] [group] [state] [brief]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface type number

Example:

Router(config)# interface fastethernet 0/0

Specifies an interface type and number, and enters interface configuration mode.

Step 4 

ip address ip-address mask [secondary]

Example:

Router(config-if)# ip address 10.21.8.32 255.255.255.0

Specifies a primary or secondary IP address for an interface.

Refer to the "Configuring IP Addressing" chapter of the Release 12.2 Cisco IOS IP Configuration Guide for information on configuring IP addresses.

Step 5 

glbp group ip [ip-address [secondary]]

Example:

Router(config-if)# glbp 10 ip 10.21.8.10

Enables GLBP on an interface and identifies the primary IP address of the virtual gateway.

After you identify a primary IP address, you can use the glbp group ip command again with the secondary keyword to indicate additional IP addresses supported by this group.

Step 6 

exit

Example:

Router(config-if)# exit

Exits interface configuration mode, and returns the router to global configuration mode.

Step 7 

show glbp [interface-type interface-number] [group] [state] [brief]

Example:

Router(config)# show glbp 10

(Optional) Displays information about GLBP groups on a router.

Use the optional brief keyword to display a single line of information about each virtual gateway or virtual forwarder.

Examples

This section provides the following output example:

Sample Output for the show glbp Command

Sample Output for the show glbp Command

In the following example, output information is displayed about the status of the GLBP group, named 10, on the router:

Router# show glbp 10

FastEthernet0/0 - Group 10
  State is Active
    2 state changes, last state change 23:50:33
  Virtual IP address is 10.21.8.10
  Hello time 5 sec, hold time 18 sec
    Next hello sent in 4.300 secs
  Redirect time 600 sec, forwarder time-out 7200 sec
  Authentication text "stringabc"
  Preemption enabled, min delay 60 sec
  Active is local
  Standby is unknown
  Priority 254 (configured)
  Weighting 105 (configured 110), thresholds: lower 95, upper 105
    Track object 2 state Down decrement 5
  Load balancing: host-dependent
  There is 1 forwarder (1 active)
  Forwarder 1
    State is Active
      1 state change, last state change 23:50:15
    MAC address is 0007.b400.0101 (default)
    Owner ID is 0005.0050.6c08
    Redirection enabled
    Preemption enabled, min delay 60 sec
    Active is local, weighting 105

Troubleshooting Gateway Load Balancing Protocol

The Gateway Load Balancing Protocol feature introduces five privileged EXEC mode commands to enable diagnostic output concerning various events relating to the operation of GLBP to be displayed on a console. The debug condition glbp, debug glbp errors, debug glbp events, debug glbp packets, and debug glbp terse commands are intended only for troubleshooting purposes because the volume of output generated by the software can result in severe performance degradation on the router. Perform this task to minimize the impact of using the debug glbp commands.

This procedure will minimize the load on the router created by the debug condition glbp or debug glbp command because the console port is no longer generating character-by-character processor interrupts. If you cannot connect to a console directly, you can run this procedure via a terminal server. If you must break the Telnet connection, however, you may not be able to reconnect because the router may be unable to respond due to the processor load of generating the debugging output.

Prerequisites

This task requires a router running GLBP to be attached directly to a console.

SUMMARY STEPS

1. enable

2. configure terminal

3. no logging console

4. Use Telnet to access a router port and repeat Steps 1 and 2.

5. terminal monitor

6. end

7. debug condition glbp interface-type interface-number group [forwarder]

8. configure terminal

9. no terminal monitor

10. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

no logging console

Example:

Router(config)# no logging console

Disables all logging to the console terminal.

To reenable logging to the console, use the logging console command in global configuration mode.

Step 4 

Use Telnet to access a router port and repeat Steps 1 and 2.

Enters global configuration mode in a recursive Telnet session, which allows the output to be redirected away from the console port.

Step 5 

terminal monitor

Example:

Router(config)# terminal monitor

Enables logging output on the virtual terminal.

Step 6 

end

Example:

Router(config)# end

Exits to privileged EXEC mode.

Step 7 

debug condition glbp interface-type interface-number group [forwarder]

Example:

Router# debug condition glbp fastethernet 0/0 10 1

Displays debugging messages about GLBP conditions.

Try to enter only specific debug condition glbp or debug glbp commands to isolate the output to a certain subcomponent and minimize the load on the processor. Use appropriate arguments and keywords to generate more detailed debug information on specified subcomponents.

Enter the specific no debug condition glbp or no debug glbp command when you are finished.

Step 8 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 9 

no terminal monitor

Example:

Router(config)# no terminal monitor

Disables logging on the virtual terminal.

Step 10 

end

Example:

Router(config)# end

Exits to privileged EXEC mode.

Configuration Examples for Gateway Load Balancing Protocol

This section contains the following configuration examples:

Customizing GLBP Configuration Example

Configuring GLBP Weighting Example

Enabling GLBP Configuration Example

Customizing GLBP Configuration Example

In the following example, Router A, shown in Figure 1, is configured with a number of GLBP commands:

interface fastethernet 0/0
 ip address 10.21.8.32 255.255.255.0
 glbp 10 authentication text stringxyz
 glbp 10 forwarder preempt delay minimum 60
 glbp 10 load-balancing host-dependent
 glbp 10 preempt delay minimum 60
 glbp 10 priority 254
 glbp 10 timers 5 18
 glbp 10 timers redirect 600 7200

Configuring GLBP Weighting Example

In the following example, Router A, shown in Figure 1, is configured to track the IP routing state of the POS interface 6/0, an initial GLBP weighting with upper and lower thresholds is set, and a weighting decrement value of 5 is set. If POS interface 6/0 goes down, the weighting value of the router is reduced.

track 2 interface POS 6/0 ip routing
interface fastethernet 0/0
 glbp 10 weighting 110 lower 95 upper 105
 glbp 10 weighting track 2 decrement 5

Enabling GLBP Configuration Example

In the following example, Router A, shown in Figure 1, is configured to enable GLBP, and the virtual IP address of 10.21.8.10 is specified for GLBP group 10:

interface fastethernet 0/0
 ip address 10.21.8.32 255.255.255.0
 glbp 10 ip 10.21.8.10

Additional References

For additional information related to GLBP, see the following sections:

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Related Documents

Related Topic
Document Title

HSRP configuration

"Configuring IP Services" chapter in the Cisco IOS IP Configuration Guide, Release 12.2

HSRP commands: complete command syntax, command mode, defaults, usage guidelines, and examples

Cisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2 T

VRRP feature

"Virtual Router Redundancy Protocol" feature document, Release 12.2(13)T


Standards

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.


MIBs

MIBs
MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

RFCs

RFCs
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.


Technical Assistance

Description
Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml


Command Reference

This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 T command reference publications.

debug condition glbp

debug glbp errors

debug glbp events

debug glbp packets

debug glbp terse

glbp authentication

glbp forwarder preempt

glbp ip

glbp load-balancing

glbp preempt

glbp priority

glbp timers

glbp timers redirect

glbp weighting

glbp weighting track

show glbp

track

debug condition glbp

To display debugging messages about Gateway Load Balancing Protocol (GLBP) conditions, use the debug condition glbp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug condition glbp interface-type interface-number group [forwarder]

no debug condition glbp type number group [forwarder]

Syntax Description

interface-type interface-number

Interface type and number for which output is displayed.

group

GLBP group number in the range from 0 to 1023.

forwarder

(Optional) Number in the range from 1 to 255 used to identify a virtual MAC address.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(14)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.


Examples

The following is sample output from the debug condition glbp command:

Router# debug condition glbp fastethernet 0/0 10 1

Condition 1 set
5d23h: Fa0/0 GLBP10.1 Debug: Condition 1, glbp Fa0/0 GLBP10.1 triggered, count 1

Related Commands

Command
Description

debug glbp errors

Displays debugging messages about GLBP errors.

debug glbp events

Displays debugging messages about GLBP events.

debug glbp packets

Displays debugging messages about GLBP packets.

debug glbp terse

Displays a limited range of debugging messages about GLBP errors, events, and packets.


debug glbp errors

To display debugging messages about Gateway Load Balancing Protocol (GLBP) error conditions, use the debug glbp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug glbp errors

no debug glbp errors

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(14)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.


Examples

The following is sample output from the debug glbp errors command:

Router# debug glbp errors

GLBP Errors debugging is on
1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found
1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found
1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found

Related Commands

Command
Description

debug condition glbp

Displays debugging messages about GLBP that match specific conditions.


debug glbp events

To display debugging messages about Gateway Load Balancing Protocol (GLBP) events that are occurring, use the debug glbp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug glbp events [all | detail | terse]

no debug glbp events [all | detail | terse]

Syntax Description

all

(Optional) Displays all debugging output about GLBP events.

detail

(Optional) Displays detailed debugging output about GLBP events.

terse

(Optional) Displays a limited range of debugging output about GLBP events.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(14)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.


Examples

The following is sample output from the debug glbp events command when the terse keyword is specified:

Router# debug glbp events terse

GLBP Events debugging is on
    (protocol, redundancy, track)

Related Commands

Command
Description

debug condition glbp

Displays debugging messages about GLBP that match specific conditions.


debug glbp packets

To display summary information about Gateway Load Balancing Protocol (GLBP) packets being sent or received, use the debug glbp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug glbp packets [all | detail | hello | reply | request | terse]

no debug glbp packets [all | detail | hello | reply | request | terse]

Syntax Description

all

(Optional) Displays all debugging output about GLBP packets.

detail

(Optional) Displays detailed debugging output about GLBP packets.

hello

(Optional) Displays debugging output about GLBP hello packets.

reply

(Optional) Displays debugging output about GLBP reply packets.

request

(Optional) Displays debugging output about GLBP request packets.

terse

(Optional) Displays a limited range of debugging output about GLBP packets.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(14)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.


Examples

The following is sample output from the debug glbp packets command:

Router# debug glbp packets hello

GLBP Packets debugging is on
    (Hello)
1d19h: GLBP: Fa0/0 Grp 10 Hello  out 10.21.8.32 VG Active  pri 254 vIP 10.21.8.10 1
1d19h: GLBP: Fa0/0 Grp 10 Hello  out 10.21.8.32 VG Active  pri 254 vIP 10.21.8.10 1
1d19h: GLBP: Fa0/0 Grp 10 Hello  out 10.21.8.32 VG Active  pri 254 vIP 10.21.8.10 1
1d19h: GLBP: Fa0/0 Grp 10 Hello  out 10.21.8.32 VG Active  pri 254 vIP 10.21.8.10 1

Related Commands

Command
Description

debug condition glbp

Displays debugging messages about GLBP that match specific conditions.


debug glbp terse

To display a limited range of debug messages about Gateway Load Balancing Protocol (GLBP) errors, events, and packets, use the debug glbp terse command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug glbp terse

no debug glbp terse

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(14)S

This command was introduced.

12.2(15)T

This command was integrated into Cisco IOS Release 12.2(15)T.


Examples

The following is sample output from the debug glbp terse command:

Router# debug glbp terse

GLBP:
  GLBP Errors debugging is on
  GLBP Events debugging is on
    (protocol, redundancy, track)
  GLBP Packets debugging is on
    (Request, Reply)

Related Commands

Command
Description

debug condition glbp

Displays debugging messages about GLBP that match specific conditions.

debug glbp errors

Displays debugging messages about GLBP errors.

debug glbp events

Displays debugging messages about GLBP events.

debug glbp packets