cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
992
Views
0
Helpful
3
Replies

3750X IPBASE And GhostCast Server

Jim R
Level 1
Level 1

Hi all,

I imagine this question has been posted a million times before but here goes.  I am trying to image a number of machines via GhostCast server across a 3750X stack running multiple VLANS.  I am running the IPBASE image so am aware that multicast functionality is limited however I was hoping someone could help me work around the issue.

I am running 12.2(55)SE3.

I have tried adding both VLAN's into an IGMP group using the "ip igmp join-group" command which shows both VLANs as part of the group but to no reall effect.  To be honest though I am clutching at straws!  I'm just starting to read through the documentation so hopefully that will help.

In the meantime any help would be appreciated!

Jamie                  

3 Replies 3

Did you try to use the all-hosts multicast address? The could (never tried) work without building the tree

Let me know

Alessio

Peter Paluch
Cisco Employee
Cisco Employee

Jamie and Alessio,

Alessio, if we are dealing with inter-VLAN multicast (i.e. the multicasts are originated in one VLAN and are supposed to be delivered into another VLAN) then using the 224.0.0.1 address will not help - apart from this IP address being purposefully defined with link local scope (i.e. not allowed to address any station on a different interface), no router will carry any multicast packet from one interface to another without multicast routing support.

I shall have a look into the docs as well. However, without multicast routing support, the only feasible way of doing this is to perform directed broadcasting.

Best regards,

Peter

Jim R
Level 1
Level 1

I think I've found a way round the issue using a stub IGMP type configuration. 

On the router I set the following commands:

ip multicast-routing distributed
ip pim rp-address 10.92.39.13 < -- address of ghostcast server


On each VLAN involved in ghosting
ip pim passive
ip igmp helper-address 10.92.39.13 <-- address of ghostcast server

Seems to do the job, a sh ip mroute shows the dynamically built IGMP groups in use (Normally different each time ghostcast server starts) and the client app finds the session name without any prompting.

Cheers all, Let me know if the above helps you at all.

Jamie

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card