*** The following is posted AS I UNDERSTAND IT and needs to be thouroughly researched before implementation ***
I guess I should've read the command reference before inquiring about the ARP cache timeout on a PIX. It appears that it's simply a matter of putting a line in like:
ARP TIMEOUT seconds
So if, in a PIX (or router), you want it repoll for the MAC address every 60 seconds, you'd add a line like:
ARP TIMEOUT 60
(In router IOS, this is done in the Interface Configuration)
The default is 14400 (4 hours). On a PIX, pay attention to ARP cache's you don't want to poll and that you want to be permanent. If your DMZ devices are static, consider adding permanent ARP entries for them (as well as the internal device the PIX is plugged in to, say the default gateway if the LAN is isolated from the PIX via it).
While administratively this can lead to more work, it might be worth it to cut down on a device continously polling for ARP resolution and increasing unwanted traffic.
Assuming that you'd have an interface on the same network as your GLBP team, in a router, you'd just configure that one interface's timeout to poll more often and rotate which team member it uses, while the others use their default timeout. On a PIX, it's a global config, and you'd want to control the ARP life of each device it touches if you don't want it constantly polling for all device's MAC addresses with the same timeout. You set a device's MAC permanently in PIX with:
ARP if_name ip_address mac_address alias
Without the alias tag, the ARP table entry will repoll at the end of the specified default timeout period (handy command in PIX when changing devices and you need an immediate MAC address replacement in the ARP table).
Anyone see any flaws with this method? I'm open to ideas.
Hope this helps..