Troubleshooting Multicast and GHOST

Where can I get a basic understanding of how GHOST works with unicast and multicast? I am not a server admin but a network engineer and have a complaint that the ghost multicast is slow and only works on one vlan? I would like to know what protocol is used and how to configure and troubleshoot a network to support GHOST.
Dragon0x40Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nayyar HH (CCIE RS)Network ArchitectCommented:
See this doc "How the Ghost Console and Client communicate over the network"

http://service1.symantec.com/SUPPORT/ghost.nsf/ppfdocs/2002101612025325

There are several phases to the communication process; Client will try to discovery server via multicast if that fails they fail over to WINS
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dragon0x40Author Commented:
There are no examples or diagrams in your link.

A couple of good tutorials for GHOST:

http://ghost.radified.com/ 

http://www.symantec.com/business/support/ghosttutorial/GhostTutorials.html

Still looking for something that explains the networking part better.
0
jburgaardCommented:
You do not mention the make of the switches that you are dealing with here.
I recently had a problem with a HP-procurve setup, where I was told that multicast did not work in a particular vlan.
Check of this vlan on all switches would show that
IP IGMP actualy WAS enabled, as it must bee for proper pruning to take place (broadcast on all ports is alternative)
however the CLI-command
SHOW IP IGMP <vlan>   was to reveal, that there was no Querier elected.
After asigning an IP to this vlan on a central switch + CLI-command:
IP IGMP QUERIER
That made the change , so after that I could observe on an other switch the uplink-port leading to the central switch named Querier.
Do you have to deal with making mulicast work between vlans?
If so IP multicast routing should also be in place, as far as i remember both sparse&dense on a HP.
HTH
0
Dragon0x40Author Commented:
I will research the querier and the mcast routing settings. These are cisco switches so the commands and defaults may be different.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.