Why can't users connect to my multi-hosted IPs?Multi-hosted IP addresses were introduced in Zeus Traffic Manager 6.0. They allow the same traffic IP to be hosted on several traffic managers at the same time. This can provide benefits to traffic distribution and reduce the number of IPs needed to run a service. Multi-hosted IPs make use of multicast messages that are broadcast by each traffic manager. These messages are received by network switches and routers to let them know where to send network packets for these IP addresses. Most switches and routers should work perfectly without any additional configuration, however sometimes you may need to tweak some settings on a switch. If you cannot contact a multi-hosted IP, first try pinging the IP in question from a machine on the same subnet as the traffic manager, and then from a machine outside of the subnet. If these ping packets are not replied to, you may need to reconfigure your switches. Cisco Catalyst switches and routersCisco Catalyst switches using the IOS software, need to be manually told about each Multi-Hosted IP's multicast MAC address, which is used to deliver the IP's incoming connections to all machines in the Traffic IP group. This can be done by logging into the CLI of the switch and using the following commands: For each Multi-Hosted IP in the Traffic IP group:
Then, for Cisco Catalyst 6000/6500 series switches:
Or for all other Catalyst switches:
Replace [MAC] with the MAC address listed on the Edit Traffic IP Groups page, and [Interfaces] with the interfaces on the switch connected to the Zeus cluster. Refer to Cisco's documentation for details. Other switchesPlease consult the documentation for your switch hardware, particularly any information regarding broadcast MAC addresses or multicast. When configuring the switch, you may need to take a note of the MAC address used for each multi-hosted IP. This information is shown on the Edit Traffic IP Groups page. Comments:This public messageboard is not a forum for technical support. To report technical support problems, please contact our dedicated Support team using the instructions at the bottom of this page.
Comment from:
mrz [Visitor]
· http://www.mozilla.com
These instructions are missing some details.
1. Any attached Layer 3 device will need to have a static arp entry. This will most commonly be the router or default gateway but will include any other hosts on the same subnet. 2. Any Layer 2 device will need to have a static MAC entry. It may not be enough to add static MAC entries to just the connected switch, however. You may need to make sure that all switches can properly flood to all switches. A couple other notes: 1. On Cisco switches you'll need to disable igmp snooping. In IOS,
2. On Juniper switches, you'll need:
21 February 2010 @ 06:07 |
Recently...
Other Resources
|
