Unicast Routing Configuration Guide, Cisco DCNM for LAN, Release 6.x
Configuring GLBP
Downloads: This chapterpdf (PDF - 224.0KB) The complete bookPDF (PDF - 2.23MB) | Feedback

Configuring GLBP

Table Of Contents

Configuring GLBP

Information About GLBP

GLBP Overview

GLBP Active Virtual Gateway

GLBP Virtual MAC Address Assignment

GLBP Virtual Gateway Redundancy

GLBP Virtual Forwarder Redundancy

GLBP Authentication

GLBP Load Balancing and Tracking

High Availability

Licensing Requirements for GLBP

Prerequisites for GLBP

Default Settings

Platform Support

Configuring GLBP

Creating a GLBP Group

Configuring GLBP Authentication

Configuring GLBP Load Balancing

Configuring GLBP Weighting and Tracking

Configuring Gateway Preemption

Customizing GLBP

Enabling a GLBP Group

Field Descriptions for GLBP

GLBP: Group Details Tab: Group Details Section

GLBP: Group Details Tab: Authentication, Gateway Preemption Section

GLBP: Group Details Tab: Weighting and Object Tracking Section

GLBP: Group Details Tab: Virtual Forwarder Setting Section

GLBP: Group Details Tab: Timers Section

GLBP: Virtual Gateways and Forwarders Tab: Forwarder Details Section

GLBP: Virtual Gateways and Forwarders Tab: GLBP Group Member Details Section

Additional References

Related Documents

Standards

Feature History for GLBP


Configuring GLBP


This chapter describes how to configure the Gateway Load Balancing Protocol (GLBP) on the Cisco Data Center Network Manager (DCNM).

This chapter includes the following sections:

Information About GLBP

Licensing Requirements for GLBP

Prerequisites for GLBP

Default Settings

Platform Support

Configuring GLBP

Field Descriptions for GLBP

Additional References

Feature History for GLBP

Information About GLBP

GLBP provides path redundancy for IP by sharing protocol and Media Access Control (MAC) addresses between redundant gateways. Additionally, GLBP allows a group of Layer 3 routers to share the load of the default gateway on a LAN. A GLBP router can automatically assume the forwarding function of another router in the group if the other router fails.

This section includes the following topics:

GLBP Overview

GLBP Active Virtual Gateway

GLBP Virtual MAC Address Assignment

GLBP Virtual Gateway Redundancy

GLBP Virtual Forwarder Redundancy

GLBP Authentication

GLBP Load Balancing and Tracking

High Availability

GLBP Overview

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

GLBP performs a similar function to the Hot Standby Redundancy Protocol (HSRP) and the Virtual Router Redundancy Protocol (VRRP). HSRP and VRRP allow multiple routers to participate in a virtual group configured with a virtual IP address. These protocols elect one member as the active router to forward packets to the virtual IP address for the group. The other routers in the group are redundant until the active router fails.

GLBP performs an additional load balancing function that the other protocols do not provide. GLBP load balances over multiple routers (gateways) using a single virtual IP address and multiple virtual MAC addresses. GLBP shares the forwarding load among all routers in a GLBP group instead of allowing a single router to handle the whole load while the other routers remain idle. You configure each host with the same virtual IP address, and all routers in the virtual group participate in forwarding packets. GLBP members communicate between each other using periodic hello messages.

GLBP Active Virtual Gateway

GLBP prioritizes gateways to elect an active virtual gateway (AVG). If multiple gateways have the same priority, the gateway with the highest real IP address becomes the AVG. The AVG assigns a virtual MAC address to each member of the GLBP group. Each member is the active virtual forwarder (AVF) for its assigned virtual MAC address, forwarding packets sent to its assigned virtual MAC address.

The AVG also answers Address Resolution Protocol (ARP) requests for the virtual IP address. Load sharing is achieved when the AVG replies to the ARP requests with different virtual MAC addresses.


Note Packets received on a routed port destined for the GLBP virtual IP address will terminate on the local router, regardless of whether that router is the active GLBP router or a redundant GLBP router. This includes ping and Telnet traffic. Packets received on a Layer 2 (VLAN) interface destined for the GLBP virtual IP address will terminate on the active router.


GLBP Virtual MAC Address Assignment

The AVG assigns the virtual MAC addresses to each member of the group. The group members request a virtual MAC address after they discover the AVG through hello messages. The AVG assigns the next MAC address based on the load-balancing algorithm selected (see the "GLBP Load Balancing and Tracking" section). A gateway that is assigned with a virtual MAC address by the AVG is the primary virtual forwarder. The other members of the GLBP group that learn the virtual MAC addresses from hello messages are secondary virtual forwarders.

GLBP Virtual Gateway Redundancy

GLBP provides virtual gateway redundancy. A member in a group can be in the active, standby, or listen state. GLBP uses a priority algorithm to elect one gateway as the AVG and elect another gateway as the standby virtual gateway. The remaining gateways go into the listen state. You can configure the GLBP priority on each gateway. If the GLBP priority is identical on multiple gateways, GLBP uses the gateway with the highest IP address as the AVG.

If an AVG fails, the standby virtual gateway assumes responsibility for the virtual IP address. GLBP elects a new standby virtual gateway from the gateways in the listen state.

GLBP Virtual Forwarder Redundancy

GLBP provides virtual forwarder redundancy. Virtual forwarder redundancy is similar to virtual gateway redundancy with an active virtual forwarder (AVF). If the AVF fails, a secondary virtual forwarder in the listen state assumes responsibility for the virtual MAC address. This secondary virtual forwarder is also a primary virtual forwarder for a different virtual MAC address. GLBP migrates hosts away from the old virtual MAC address of the failed AVF, using the following two timers:

Redirect timer—Specifies the interval during which the AVG continues to redirect hosts to the old virtual MAC address. When the redirect time expires, the AVG stops using the old virtual MAC address in ARP replies, although the secondary virtual forwarder continues to forward packets that were sent to the old virtual MAC address.

Secondary hold timer—Specifies the interval during which the virtual MAC address is valid. When the secondary hold time expires, GLBP removes the virtual MAC address from all gateways in the GLBP group and load balances the traffic over the remaining AVFs. The expired virtual MAC address becomes eligible for reassignment by the AVG.

GLBP uses hello messages to communicate the current state of the timers.

In Figure 4-1, router A is the AVG for a GLBP group and is responsible for the virtual IP address 192.0.2.1. 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 192.0.2.1, the virtual IP address, and a gateway MAC address of 0007.b400.0101 that points to router A. 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 4-1 GLBP Topology

If router A becomes unavailable, client 1 does not lose access to the WAN because router B assumes 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 also assumes 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 Authentication

GLBP has three authentication types:

MD5 authentication

Plain text authentication

No authentication

MD5 authentication provides greater security than plain text authentication. MD5 authentication allows each GLBP group member to use a secret key to generate a keyed MD5 hash that is part of the outgoing packet. At the receiving end, a keyed hash of an incoming packet is generated. If the hash within the incoming packet does not match the generated hash, the packet is ignored. The key for the MD5 hash can either be given directly in the configuration using a key string or supplied indirectly through a key chain.

You can also choose to use a simple password in plain text to authenticate GLBP packets or choose no authentication for GLBP.

GLBP rejects packets in any of the following cases:

The authentication schemes differ on the router and in the incoming packet.

MD5 digests differ on the router and in the incoming packet.

Text authentication strings differ on the router and in the incoming packet.

GLBP Load Balancing and Tracking

You can configure the following load-balancing methods for GLBP:

Round-robin—GLBP cycles through the virtual MAC addresses sent in ARP replies, load balancing the traffic across all the AVFs.

Weighted—AVG uses the advertised weight for an AVF to decide the load directed to the AVF. A higher weight means that the AVG directs more traffic to the AVF.

Host dependent—GLBP uses the MAC address of the host to determine which virtual MAC address to direct the host to use. This algorithm guarantees that a host gets the same virtual MAC address if the number of virtual forwarders does not change.

The default for IPv4 networks is round-robin. You can disable all load balancing for GLBP on an interface. If you do not configure load balancing, the AVG handles all traffic for the hosts while the other GLBP group members are in standby or listen mode.

You can configure GLBP to track an interface or routes and enable the secondary virtual forwarder to take over if a tracked link goes down. GLBP tracking uses weighted load-balancing to determine whether a GLBP group member acts as an AVF. You must configure the initial weighting values and optional thresholds to enable or disable this group member as an AVF. You can also configure the interface to track and the value that will reduce the interface's weighting if the interface goes down. When the GLBP group weighting drops below the lower threshold, the member is no longer an AVF and a secondary virtual forwarder takes over. When the weighting rises above the upper threshold, the member can resume its role as an AVF.

Figure 4-2 shows an example of GLBP tracking and weighting.

Figure 4-2 GLBP Object Tracking and Weighting

In Figure 4-2, the Ethernet 1/2 interface on router 1 is the gateway for host 1 (the AVF for virtual MAC address, vMAC1), while Ethernet 2/2 on router 2 acts as a secondary virtual forwarder for Host 1. Ethernet 1/2 tracks Ethernet 3/1, which is the network connection for router 1. If Ethernet 3/1 goes down, the weighting for Ethernet 1/2 drops to 90. Ethernet 2/2 on router 2 preempts Ethernet 1/2 and takes over as AVF because it has the default weighting of 100 and is configured to preempt the AVF.

See the "Configuring GLBP Weighting and Tracking" section for details about configuring weighting and tracking.

High Availability

GLBP supports stateful restarts and stateful switchover. A stateful restart occurs when the GLBP process fails and is restarted. A stateful switchover occurs when the active supervisor switches to the standby supervisor. Cisco NX-OS applies the run-time configuration after the switchover.

Licensing Requirements for GLBP

The following table shows the licensing requirements for this feature:

Product
License Requirement

Cisco DCNM

GLBP requires a LAN Enterprise license. For a complete explanation of the Cisco DCNM licensing scheme and how to obtain and apply licenses, see the Cisco DCNM Installation and Licensing Guide, Release 6.x.

Cisco NX-OS

GLBP requires no license. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For an explanation of the Cisco NX-OS licensing scheme for your platform, see the licensing guide for your platform.


Prerequisites for GLBP

The following prerequisites are required for using this feature on Cisco DCNM. For a full list of feature-specific prerequisites, see the platform-specific documentation.

GLBP has the following prerequisites:

System-message logging levels for the GLBP feature must meet or exceed Cisco DCNM requirements. During device discovery, Cisco DCNM detects inadequate logging levels and raises them to the minimum requirements. Cisco Nexus 7000 Series switches that run Cisco NX-OS Release 4.0 are an exception. For Cisco NX-OS Release 4.0, prior to device discovery, use the command-line interface to configure logging levels to meet or exceed Cisco DCNM requirements. For more information, see the Cisco DCNM Fundamentals Configuration Guide, Release 6.x.

You can only configure GLBP on Layer 3 interfaces (see the Cisco DCNM Interfaces Configuration Guide, Release 6.x).

Default Settings

Table 4-1 lists the default settings for GLBP parameters.

Table 4-1 Default GLBP Parameters 

Parameters
Default

Authentication

No authentication

Forwarder preemption delay

30 seconds

Forwarder timeout

14400 seconds

Hello timer

3 seconds

Hold timer

10 seconds

GLBP feature

Disabled

Load balancing

Round robin

Preemption

Disabled

Priority

100

Redirect timer

600 seconds

Weighting

100


Platform Support

The following platform supports this feature. For platform-specific information, including guidelines and limitations, system defaults, and configuration limits, see the corresponding documentation.

Platform
Documentation

Cisco Nexus 7000 Series switches

Cisco Nexus 7000 Series Switches Documentation


Configuring GLBP

You can access GLBP from the Routing feature selection.

For more information about the Data Center Network Manager features, see the Cisco DCNM Fundamentals Configuration Guide, Release 6.x.

This section includes the following topics:

Creating a GLBP Group

Configuring GLBP Authentication

Configuring GLBP Load Balancing

Configuring GLBP Weighting and Tracking

Configuring Gateway Preemption

Customizing GLBP

Enabling a GLBP Group

Creating a GLBP Group

You can create a GLBP group on an interface.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 From the menu bar, choose Actions > New GroupSetting.

The system highlights the new GLBP row in the Summary pane, and tabs update in the Details pane.

Step 4 From the highlighted Interface field, select the interface that you want to configure a GLBP group on from the drop-down list.

Step 5 From the Group ID field, enter the group number for this group.

The range is from 0 to 1023.

The system creates the new group on the device and highlights the new GLBP group in the Summary pane, and tabs update in the Details pane.

Step 6 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 7 From the Group Details tab, expand the Group Details section.

The basic group information appears in the Details pane.

Step 8 (Optional) From the Priority field, enter the priority for this GLBP group member.

Step 9 (Optional) From the Group Name field, enter a name for this GLBP group member.

Step 10 From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring GLBP Authentication

You can configure GLBP to authenticate the protocol using cleartext or an MD5 digest. MD5 authentication uses a key chain (see the Cisco DCNM Security Configuration Guide, Release 6.x).

BEFORE YOU BEGIN


Note You must configure the same authentication and keys on all members of the GLBP group.


DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure authentication on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Authentication, Gateway Preemption section.

The authentication information appears in the Details pane.

Step 6 From the Authentication area, from the Method drop-down list, choose the authentication method.

Step 7 (Optional) For text authentication, in the password field, enter the password string.

Step 8 (Optional) For MD5 authentication, check either Key or Key Chain.

Step 9 (Optional) For the Key option, in the key field, enter the key string and check encrypted for an encrypted key string.

Step 10 (Optional) For the Key Chain option, from the key chain drop-down list, choose the key chain that you want to use.

Step 11 From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring GLBP Load Balancing

You can configure GLBP to use load balancing based on round-robin, weighted, or host-dependent methods (see the "GLBP Load Balancing and Tracking" section).

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure load balancing on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Group Details section.

The basic group information appears in the Details pane.

Step 6 From the Method drop-down list, choose the load-balancing method.

Step 7 From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring GLBP Weighting and Tracking

You can configure GLBP weighting values and object tracking to work with the GLBP weighted load-balancing method.

You can optionally configure the interface to preempt an AVF if the interface was originally assigned with the virtual MAC address or if this interface has a higher weight than the AVF.

BEFORE YOU BEGIN

Ensure that you have configured the object tracking entry that you want to use to modify GLBP weighting (see the "Configuring Object Tracking" section).

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure weighting and tracking on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Weighting and Object Tracking section.

The weighting and object tracking information appears in the Details pane.

Step 6 From the Weight area, enter the maximum, lower threshold, and upper threshold weighting values.

Step 7 From the GLBP Tracking area, right-click and choose Add TrackObject from the pop-up menu.

Step 8 From the object ID drop-down list, choose the object ID that you want to use to modify the GLBP weighting value with.

Step 9 In the Weight Decrement field, enter the value that you want to decrement the GLBP weighting with if the tracked object state goes down.

Step 10 (Optional) From the Group Details tab, expand the Virtual Forwarder Setting section.

The virtual forwarders information appears in the Details pane.

Step 11 (Optional) Check Virtual Forwarder Preemption.

Step 12 (Optional) In the Preemption Delay field, enter the delay value in seconds.

Step 13 From the menu bar, choose File > Deploy to apply your changes to the device.


Configuring Gateway Preemption

You can configure gateway preemption.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure authentication on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Authentication, Gateway Preemption section.

The preemption information appears in the Details pane.

Step 6 From the Authentication, Gateway Preemption section, check Gateway Preemption.

Step 7 From the Minimum Delay field, enter the minimum delay to wait before preemption occurs.

The default is 3600 seconds.

Step 8 From the menu bar, choose File > Deploy to apply your changes to the device.


Customizing GLBP

Customizing the behavior of GLBP is optional. Be aware that as soon as you enable a GLBP group by configuring a virtual IP address, that group is operational. If you enable a GLBP group before you customize GLBP, the router could take over control of the group and become the AVG before you finish customizing the feature. If you plan to customize GLBP, you should do so before enabling GLBP.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure timers on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Timers section.

The timers information appears in the Details pane.

Step 6 From the Configured Timers area, in the Hello Time (msec) field, enter the hello time.

Step 7 From the Configured Timers area, in the Hold Time (msec) field, enter the hold time.

Step 8 From the Configured Timers area, in the Redirect Time (sec) field, enter the redirect time.

Step 9 From the Configured Timers area, in the Forwarder Time-out (sec) field, enter the hold time.

Step 10 From the menu bar, choose File > Deploy to apply your changes to the device.


Enabling a GLBP Group

You can configure the virtual IP address on an interface to enable the GLBP group. You must configure each gateway in the GLBP group with the same group number. The GLBP member can learn all other required parameters from another GLBP member.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Routing > Gateway Redundancy > GLBP.

The available devices appear in the Summary pane.

Step 2 From the Summary pane, click the device that you want to configure GLBP on.

Step 3 Click the group that you want to configure timers on.

Step 4 From the Details pane, click the Group Details tab.

The Group Details tab appears.

Step 5 From the Group Details tab, expand the Group Details section.

The general information appears in the Details pane.

Step 6 (Optional) To manually set the virtual IP address, enter an IP address in the Virtual IP address field.

Step 7 (Optional) To learn the virtual IP address, check Learn Virtual IP from Members Of Group.

Step 8 (Optional) From the Virtual Secondary IP Address field, enter a secondary IP address.

Step 9 From the menu bar, choose File > Deploy to apply your changes to the device.


Field Descriptions for GLBP

This section includes the following field descriptions for GLBP:

GLBP: Group Details Tab: Group Details Section

GLBP: Group Details Tab: Authentication, Gateway Preemption Section

GLBP: Group Details Tab: Weighting and Object Tracking Section

GLBP: Group Details Tab: Virtual Forwarder Setting Section

GLBP: Group Details Tab: Timers Section

GLBP: Virtual Gateways and Forwarders Tab: Forwarder Details Section

GLBP: Virtual Gateways and Forwarders Tab: GLBP Group Member Details Section

GLBP: Group Details Tab: Group Details Section

Table 4-2 GLBP: Group Details: Group Details 

Field
Description
Gateway

Group ID

Display only. Group number for the GLBP group.

Priority

Priority for the group member, used for AVG selection.

Group Name

Name for the GLBP group.

Method

Load balancing method for this GLBP group.

Gateway State

Display only. Administrative state for the group member.

State Change Count

Display only. Number of times the GLBP gateway state changed.

Last State Change

Display only. Time of the last GLBP gateway state change.

Active Gateway

IP Address

Address of active gateway.

Priority

Priority of active gateway.

Standby Gateway

IP Address

Address of standby gateway.

Priority

Priority of standby gateway.

IP Address Settings

Learn Virtual IP from Members of Group

Learned IP address for the group.

Virtual IP Address

Virtual IP address for the group.

Secondary IP Address

Secondary IP address for the group.


GLBP: Group Details Tab: Authentication, Gateway Preemption Section

Table 4-3 GLBP: Group Details: Authentication, Gateway Preemption  

Field
Description
Authentication

Method

Authentication method.

Password

Password for text authentication.

Key

Key string for MD5 authentication.

Encrypted

Key string is encrypted for MD5 authentication.

Key Chain

Key chain name for MD5 authentication.

Gateway Preemption

Gateway Preemption

Gateway preemption.

Minimum Delay

Minimum delay to wait before preemption occurs.


GLBP: Group Details Tab: Weighting and Object Tracking Section

Table 4-4 GLBP: Group Details: Weighting and Object Tracking 

Field
Description
Weight

Maximum

Maximum weighted value.

Lower Threshold

Lower threshold of weighted value.

Upper Threshold

Upper threshold of weighted value.

GLBP Tracking

Object ID

ID of object to track.

Tracked Object

Detail of tracked object.

Weight Decrement

Value to decrement the GLBP weight if the tracked object goes down.


GLBP: Group Details Tab: Virtual Forwarder Setting Section

Table 4-5 GLBP: Group Details:Virtual Forwarder Setting  

Field
Description

Forwarder ID

ID of virtual forwarder.

Virtual MAC Address

Virtual MAC address for the GLBP group.

Virtual Forwarder Preemption

Device that takes over as the AVF for a GLBP group if the current AVF for a GLBP group falls below its low weighting threshold.

Preemption Delay

Delay before virtual forwarder preemption occurs.


GLBP: Group Details Tab: Timers Section

Table 4-6 GLBP: Group Details:Timers 

Field
Description
Active Timer Values

Hello Time

Display only. GLBP group hello time.

Hold Time

Display only. GLBP group hold time.

Virtual Forwarder Redirect Time

Display only. The time interval in seconds during which the active virtual gateway continues to redirect clients to an active virtual forwarder.

Secondary Forwarder Hold Time

Display only. The interval in seconds before a secondary virtual forwarder becomes invalid.

Configured Timers

Hello Time

GLBP group hello time.

Hold Time

GLBP group hold time.

Virtual Forwarder Redirect Time

Time interval in seconds during which the active virtual gateway continues to redirect clients to an active virtual forwarder.

Secondary Forwarder Hold Time

Interval in seconds before a secondary virtual forwarder becomes invalid.


GLBP: Virtual Gateways and Forwarders Tab: Forwarder Details Section

Table 4-7 GLBP:Virtual Gateways and Forwarders:Forwarder Details 

Field
Description

Forwarder ID

Display only. ID of virtual forwarder.

MAC Address

Display only. MAC address for the GLBP group.

Virtual MAC Address

Display only. Virtual MAC address for the GLBP group.

Redirection

Display only. Redirection state.

Weighting

Display only. Weighting value for this forwarder.

Gateway State

Display only. Administrative state for the group member.

State Change Count

Display only. Number of times the GLBP gateway state changed.

Last State Change

Display only. Time of the last GLBP gateway state change.


GLBP: Virtual Gateways and Forwarders Tab: GLBP Group Member Details Section

Table 4-8 GLBP:Virtual Gateways and Forwarders:GLBP Group Member Details 

Field
Description

IP Address

IP address of the group member.

MAC Address

MAC address of the group member.


Additional References

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

Related Documents

Standards

Related Documents

Related Topic
Document Title

Configuring the Hot Standby Redundancy protocol

Chapter 5 "Configuring HSRP"

GLBP CLI commands

Cisco Nexus 7000 Series NX-OS Unicast Routing Command Reference, Release 6.x

Configuring high availability

Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide, Release 6.x


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.


Feature History for GLBP

Table 4-9 lists the release history for this feature.

Table 4-9 Feature History for GLBP

Feature Name
Releases
Feature Information

GLBP

4.0(1)

This feature was introduced.