 a useful protocol, but I find it pretty frustrating to troubleshoot. Look at the paragraph for the active forwarder: Forwarder 2 State is Active 1 state change, last state change 00:00:44 MAC address is 0007.b400.0a02 (default) Owner ID is 0012.43b9.2c70 Redirection enabled Preemption enabled, min delay 30 sec Active is local, weighting 50 We can tell that forwarder 2 is active, but we don't know which router is forwarder 2. We didn't name them 1,2,3, yet the router has labeled them as such. GLBP does tell us what the MAC address of the owner is, and we can cross-reference that with the group members listed earlier in the output: Group members: 0012.43b9.2020 (10.0.0.4) 0012.43b9.2c70 (10.0.0.2) local 001c.588b.f6a8 (10.0.0.3) Call me old and get off my lawn, but I believe that information should all be within the forwarder paragraph. Irritations aside, GLBP is invaluable if you would like to utilize more than one gateway at a time while being able to have a single virtual gateway address. Another nice GLBP command is show glbp brief, which gives a simpler overview of how GLBP is configured and operating: R1#sho glbp brief Interface Pri State Address Active router Standby router Fao/o Active 10.0.0.1 local 10.0.0.3 Fao/o Listen 0007.b400.0a01 10.0.0.3 Fao/o Active 0007.b400.0a02 local Fao/o Listen 0007.b400.0a03 10.0.0.4 Object Tracking in GLBP Like HSRP's interface tracking, GLBP can be configured to track the status of another interface. Even better, GLBP uses something called object tracking, which lets you track much more than simple up/down status. First we need to configure an object to track. Here, I'll configure a new object, number 2, which is the line-protocol status on F0/1: (config)#track 2 interface FastEtherneto/1 line-protocol Object tracking is a powerful tool that can track more than just interface status. For example, you can use it to track response times across a link using the Response Time Reporter (RTR), and then disable a gateway in GLBP when response times get too high. You can also use 