I was kind of curious on something. I recently changed my ssm static maps to directly specify which multicast source a particular multicast would be coming from. This is coming from a provider outside of my network.
ip igmp ssm-map static 40 10.0.10.3
ip igmp ssm-map static 41 10.0.10.4
ip igmp ssm-map static 42 10.0.10.5
I then have specific multicast with them access-lists:
access-list 41 permit 126.96.36.199
This obviously creates a really nice sh ip mroute 188.8.131.52 entry with a one to one mapping. What I had before was a more generic access-list with all the hosts pointint to the same access-list:
ip igmp ssm-map static 30 10.0.10.3
ip igmp ssm-map static 30 10.0.10.4
ip igmp ssm-map static 30 10.0.10.5
Then i created a more generic access-list like:
access-list 30 permit 184.108.40.206 0.0.255.255
which was really nice. The only problem is that it created a mapping in the mroute table for each specific host. That is what the router is supposed to do and was expected. The problem with the way i'm doing it now is that my multicast provider could change a multicast to a different source. I would have the source address in my table, but I don't have the friendly access-list like I had with the /16. I was wondering if there is any harm on doing it the way I had it in the first place even though I could actually get up to 20 entries of sources and one is really only active. I hope this makes sense, just trying to figure out the easiest way to accomplish this with ssm or the best way I guess. Looking for opinions.
I have a question about SSM DNS and static mapping.
Let's say we already have SSM with DNS mapping and it works fine. I want now to add a new source and source group
but I do not want to add a DNS record. Can I create a static mapping without disabling the working SSM DNS mapping configuration?
I found this on cisco.com but I have to be sure that I will not disable the working SSM DNS mappings!
Static SSM Mapping
SSM static mapping enables you to configure the last hop router to use a static map to determine the sources sending to groups. Static SSM mapping requires that you configure access lists (ACLs) to define group ranges. The groups permitted by those ACLs then can be mapped to sources using the ip igmp static ssm-map command.
You can configure static SSM mapping in smaller networks when a DNS is not needed or to locally override DNS mappings that may be temporarily incorrect. When configured, static SSM mappings take precedence over DNS mappings.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...