IPTV Multicast address range

Does anybody know what the multicast IP range is for Cisco IPTV?
I need to setup an access-list to for an RP to be used just for IPTV.

If a program uses a multicast address starting with 224.n.n.n, the announcement uses the standard sdp announcement address, and all sdp tools and all other IP/TV Content Managers within the TTL limit of the program receive it.
However, if a program uses an administratively scoped IP multicast address (the range starting at 239.0.0.0), the program announcement uses the highest address of the administratively scoped address range set in your preferences
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/iptv/v32/administration/guide/chap7.html#wp1014145

Similar Messages

IPv4 Multicast address range

Hello there.
How can we classify the IPv4 multicast range ( 224.0.0.0 - 239.255.255.255 ) in terms of Public or Private addresses ?
regards.

It's a mixture of private and public addresses depending on the particular subnet within that range. See below
http://en.wikipedia.org/wiki/Multicast_address

Clusters cannot use the same multicast address

Hello All,
Found following error while starting of managed server in weblogic.
error***
<Aug 22, 2012 4:40:57 AM GMT-06:00> <Error> <Cluster> <BEA-000166> <Some other c
luster in this domain is configured to use the same multicast address as OIM_CLU
STER. Clusters cannot use the same multicast address.>
error***
I have three managed server and two cluster.
CLUSTER NAME >> MANAGED SERVERS IN CLUSTER
OIM_CLUSTER >> admin server and oim_server1
SOA_CLUSTER >> SOA_SERVER1.
I am starting servers through cammand prompt. In cammand prompt i see above error.
How can i correct the above error ?
Thanks in advance,
Manohar

Change the multicast address: http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/pagehelp/Corecoreclusterclusterconfigmulticasttitle.html
"The multicast address used by cluster members to communicate with each other.
The valid range is from from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0. You should avoid using multicast addresses in the range x.0.0.1
This address should be unique to this cluster and should not be shared by other applications."
Some general information on clusters: http://docs.oracle.com/cd/E21764_01/apirefs.1111/e13952/pagehelp/Corecoreclustercreateclusterpagetitle.html

Multicast address on 2504

Hi all,
Today while configuring a new 2504 controller , I came across a field called Multi cast Address.
I always configure a new controller by accessing it through the console , and inputting the long list of questions.
But (if my memory is correct ) I have never come across the prompt asking to enter multi cast address . Probably because its some different code .
What does it mean ? I mean I tried entering some ip address but it showed ... Invalid muticast ip address .
Sent from Cisco Technical Support Android App

Hi,
""Snip""
The multicast address is used by the controller in order to forward traffic to access points. It is important that it does not match another address in use on your network by other protocols. For example, if you use 224.0.0.251, it breaks mDNS used by some third party applications. It is recommended that the address be on the private range (239.0.0.0-239.255.255.255, which does not include 239.0.0.x and 239.128.0.x.)
""Snip""
Reference: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080810880.shtml
HTH
Amjad
Sent from Cisco Technical Support iPad App

Limitation on source group with services using ip address range

Hello,
I have an interface on CSS which I regard as public and another interface I regard as private. On the private interface is a server farm with private ip addresses. Since the server admin guys insisted the servers need to access internet just for Windows Update, I made a source group to NAT the private addresses to public addresses to allow the servers to access internet.
I defined services for use by the source group. Since keepalive is not important in this case, I set keepalive none to ,I hope so, save system resources.
I have server 192.168.1.1-5 (5 servers) and 192.168.1.11-14 (4 servers), so I made a service with ip address 192.168.1.1 range 5 and another service 192.168.1.11 range 4.
But then I found that the two services cannot be put in the same source group. It is because of the different range in the service definition.
I can get it work if I define services with single ip address, but then I will have a long configuration with repetative information. And I think this may be using more system resources.
I can also get it work if I include 192.168.11.15 and define two services both with a range of 5 ip addresses. But 192.168.11.15 is not actually there.
Why is there such a limitation on source group, or services with ip address range? Is there the same limitation for content rules? Or am I getting it all wrong and should do the configuration in other ways?
Advices will be welcomed.
CT Yau
Hong Kong

Yes you are correct. There is a limitation while adding services into source groups.
You can create as many services that share an ip range (eg. a /24 subnet range). But the trouble starts when you add them into source groups. You can not add them into a source group NOR you can add them under different source groups as well.
You mentioned that you can use single ip adress instead of range for the services...but it is not true as you will be stuck when you add them into source groups.
I can think of these following options in your case.
Option 1
Change the ip range on the servers. Use 2 different IP ranges one for those 5 servers and another for those 4 servers.
Create 2 services for each range.
Create 2 groups and add the services.
service server-out-192.168.1.1-5
ip address 192.168.1.1 range 5
active
service server-out-172.168.1.11-14
ip address 192.168.1.11 range 4
active
group server-out-192.168.1.11-14
vip address x.x.x.1
add server-out-192.168.1.1-5
active
group server-out-172.168.1.11-14
vip address x.x.x.2
add server-out-172.168.1.11-14
active
Option 2
Create a service that includes all the ip addresses starting from 192.168.1.1 through .14 using the range keyword.
Now you need to create one source group with a VIP. Add the service to the source group.
If you do not want to cover the unassigned ip addresses just move them up and use consecutive ones.
service server-out-192.168.1.1-14
ip address 192.168.1.1 range 14
active
group server-out-192.168.1.11-14
vip address x.x.x.x
add service server-out-192.168.1.1-14
active
thanks

Memory address range - Solaris 10

Hi All,
Is there any command in Solaris 10 to know the memory address range ( hex) of each DIMM ?
How to calculate the size of the module based on the address range ?
Thanks in advance

Hi All,
Is there any command in Solaris 10 to know the memory address range ( hex) of each DIMM ?
How to calculate the size of the module based on the address range ?
Thanks in advance

PTR issues once the IP address range has been delegated to our name servers

In the past, with only a DSL line, our ISP provided our forward and reverse dns entries for our zone and we never had problems with outgoing email. Recently, we've upgraded to a managed T1 line and have decided to run our own name servers on two xserves (one on the T1 subnet and one on a DSL line). Now, many email servers won't accept mail from a mail server without a matching PTR record. We've had our ISP delegate authority of our IP address range to us.
With DNS service on, I've checked that our named.conf file refers to the db.xxx.xxx.xxx file contained in /var/named/ which contains the correct PRT entry: xxx.xxx.xxx.xxx.in-addr.arpa. IN PTR xserve.example.com.
However, when using an external DNS server a "host name for address" search in Network Utility using the IP address, it only replies with:
xxx.xxx.xxx.xxx.in-addr.arpa. 166154 IN CNAME 202.192/xxx.xxx.xxx.xxx.in-addr.arpa. Which refers to the IP range that our ISP has delegated to us.
When using our xserve as the DNS server, the host name is returned correctly, though.
Any thoughts? I've double checked with our ISP and they say they have delegated the IP address block to us.
Xserve G5 Mac OS X (10.4.8)
Xserve G5 Mac OS X (10.4.8)
Xserve G5 Mac OS X (10.4.8)
Xserve G5 Mac OS X (10.4.8)

We had a similar problem in the past and could not explain why it was not working. The reason simply was that our carrier (the ISP owning the IP addresses) reserved the right to set PTR records only on their systems. Therefore our PTR record was simply ignored.
So I would recommend contacting the support of your ISP/carrier, explaining your issue and let them set up the PTR record on their DNS properly.
Edit: Sorry, noticed that it has been solved already; for any reason I saw only your first post. So ignore my reply.

QoS binding limited to IP address range and SSID on WLAN

Our VLAN id 2 is used only by a WLAN SSID
Defining a QoS profile as using VLAN id 2 did not work. No upper rate limitation worked
Only using the IP address range of the VLAN or the SSID appeared to work.
It does not appear consistent, when a VLAN id can be specified on a WLAN in the Wireless Basic Setting Table
It is also inconsistent, that the proper SSIDs are not listed in the drop down box on the
Add / Edit Profile Binding Configuration page. They only appear as AP-1, AP-2 etc.

Has this been fixed under firmware 1.0.4.17? I cannot get this work with any type of Traffic Selector (IP/MAC/VLAN/DSCP/SSID).
Any suggestions are greatly appreciated. Thanks!

Cisco ASA 5512x - Restrict email delivery to ip address range..

Hi,
I was wondering how to tighten the security of my email delivery to a range of ip addresses (I know how on my old firewall but the cisco is quite a bit different). Right now anyone sending email to a particular ip address on my firewall can do so. I want to restrict that to two ip address ranges it will accept deliver from. I'm thinking I need two network objects for the two ranges then add to a network object group. Can anyone help with configuring the ACL for delivery using that group if I'm correct about that?
TIA
Al

Hi,
I assume that you have a server or multiple servers on your network behind the ASA and want to restrict SMTP traffic to them and only allow SMTP traffic from certain address ranges?
You might have something like this configured for the server Static NATs
objec network SMTP-SERVER1
host 10.10.10.10
(dmz,outside) static x.x.x.x dns
object network SMTP-SERVER2
host 10.10.10.20
(dmz,outside) static y.y.y.y dns
If so you could simply create the following kind of configurations to restrict traffic to them
object-group network SMTP-SERVERS
network-object object SMTP-SERVER1
network-object object SMTP-SERVER2
object-group network ALLOWED-SMTP-SOURCE
network-object
network-object
network-object host
access-list OUTSIDE-IN remark Allowed SMTP connections
access-list OUTSIDE-IN permit tcp object-group ALLOWED-SMTP-SOURCE object-group SMTP-SERVERS eq smtp
access-group OUTSIDE-IN in interface outside
The above configuration does the following
Has 2 example Static NAT configurations for local DMZ servers
Groups those 2 servers to their own object-group SMTP-SERVERS (for easier use in the ACLs)
Creates an object-group that will contain all the public networks and host addresses that are allowed to contact your SMTP servers (for easier use in the ACLs)
Configures an ACL that allows SMTP (TCP/25) connections from "outside" only if the source network for the connection belongs to some address range on the ALLOWED-SMTP-SOURCE object-group and when the destination is either one of your SMTP servers.
Naturally the above object/object-group, access-list and interface names could be different and same for the actual IP addresses.
Also, if you already have an ACL attached to your "outside" interface then naturally you use that and DONT NEED the "access-group" command above. (As its used to attach an ACL to interface which doesnt already have one attached)
- Jouni

Connecting 2 WAN clouds on the same IP address range.

Hello, I have a problem connecting my office to two third party companies.
I have two Cisco 1700 series WAN links to my office from these companies, Both routers are fully managed by their respective companies, both use static routing, and both are using the 10.0.0.0/8 IP address range.
The first company assigned my office the address range 10.212.1.0/24.
The second company assigned my office the address range 10.215.1.0/24.
My office can be set to any IP address range.
My questions are:
Is it possible to have a connection from my office to both networks at the same time? If so how?
Do I require these companies to provide me with their static routing information? or can I use routing protocols?
Do I need to perform NAT?
Can I use a PIX 515e firewall with three interfaces?
Sample configuration would be greatly appreciated

It's possible to have connections to your offices at the same time with the usage of subinterfaces.The usage of static and dynamic protocols depends totally based on the size of the topology of your network.If it's a very very small network static routing will do. Performing a nat totally depends upon ypur decision whether to use a public ip or not.If required you can use a pix firewall

IP address range of Microsoft Location Services API

Hi,
I am developing a LOB windows 8.1 application. The windows 8 tablet device we are using needs to be locked down by IP address to the specific services that the application will use. I have not been able to find the IP address range for the Microsoft Location
Sevices API uses (Windows.Devices.Geolocation namespace).
Does someone know where on the MS website this sort of information is held as I can't seem to find this information anywhere?
Thanks

Probably you can find more information from here:
https://msdn.microsoft.com/en-us/library/windows/desktop/dd464636(v=vs.85).aspx
As I understand system have a location service and when the app calls the service, the service query the location automatically.
If you still have questions about location service, perhaps ask at desktop forum is a better choice:
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=windowsgeneraldevelopmentissues
--James
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to Setup Multicast Address on Solaris 2.6 (Back to the well again)

          Basic Cluster Query,
          Several weeks ago, I was thrashing about trying to verify the syntax for setting
          up a multicast address on Solaris 2.6 in preparation for implementing Weblogic
          6.0 clustering. The command syntax was:
          ifconfig {interface}:{virtual#} plumb
          ifconfig {interface}:{virtual#} {multicast_address} up
          The commands succeeded on the first and second servers without errors, but unbeknownst
          to me there were errors reported on the second host concerning duplicate address.
          The errors were:
          unix: WARNING: IP: Hardware address '08:00:20:a6:ed:0a'
          trying to be our address 237.000.000.008!
          The server halted today after several weeks; however, it is not clear whether
          the multicast address caused the halt. Neither Weblogic nor Sun documentation
          have been helpful. Can anyone provide guidance on setting up multicast address
          on Solaris 2.6?
          Bewildered,
          Dan


Dan,
          I don't think that BEA specifically takes any stand regarding the
          configuration of operating systems. The problem is that the
          administration of Unix machines and networking is a very complex and
          sensitive subject for most companies (e.g., they have entire departments
          dedicated to this) and BEA tries not to enforce any more configuration
          specifications than it has to.
          With regards to multicast, most newer versions of the major operating
          systems (including Solaris) have support for multicast turned on "out of
          the box". However, it is possible for your administrator to muck around
          with your machine's network settings so that multicast does not work
          properly or is disabled entirely. Most people in BEA support do not
          know enough about low-level Unix TCP/IP administration to be able to
          properly guide you to "configure multicast" if it is not working
          properly. Even if they did, we wouldn't know what your administrator
          might have done or why they did what they did so it is generally best to
          get your Unix administrators involved because they really (should) have
          the knowledge of the machine's configuration.
          We do, however, provide a Java utility program called
          utils.MulticastTest that can help you to determine whether or not
          multicast is working correctly on your machine.
          Hope this helps,
          Robert
          Dan wrote:
          > Dennis,
          >
          > Thank you for the reply. I have tried working through the support line and
          > even opened a case, but BEA will not provide any guidance on system or platform
          > specific multicast addressing. They wouldn't even confirm the fact that "nothing"
          > had to be done in Solaris; however, I did not mention your comments. I don't
          > know why BEA takes such a position for common or well known architectures like
          > Solaris, AIX, or HP/UX. Thanks again for your comments.
          >
          > Sincerely,
          > Dan
          >
          >
          > "Dennis Munsie" <[email protected]> wrote:
          >
          >>Hi,
          >>
          >>Multicast addresses do not need to be set from the command line. Multicast
          >>addresses are independent of the normal IP address for an interface,
          >>and
          >>they are specified programatically when a socket is opened.
          >>
          >>--
          >>Dennis Munsie
          >>Developer Relations Engineer
          >>BEA Support
          >>
          >>"Dan" <[email protected]> wrote in message
          >>news:[email protected]...
          >>
          >>>Basic Cluster Query,
          >>>
          >>> Several weeks ago, I was thrashing about trying to verify the syntax
          >>>
          >>for
          >>setting
          >>
          >>>up a multicast address on Solaris 2.6 in preparation for implementing
          >>>
          >>Weblogic
          >>
          >>>6.0 clustering. The command syntax was:
          >>>
          >>> ifconfig {interface}:{virtual#} plumb
          >>> ifconfig {interface}:{virtual#} {multicast_address} up
          >>>
          >>>The commands succeeded on the first and second servers without errors,
          >>>
          >>but
          >>unbeknownst
          >>
          >>>to me there were errors reported on the second host concerning duplicate
          >>>
          >>address.
          >>
          >>> The errors were:
          >>>
          >>> unix: WARNING: IP: Hardware address '08:00:20:a6:ed:0a'
          >>> trying to be our address 237.000.000.008!
          >>>
          >>>The server halted today after several weeks; however, it is not clear
          >>>
          >>whether
          >>
          >>>the multicast address caused the halt. Neither Weblogic nor Sun
          >>>
          >>documentation
          >>
          >>>have been helpful. Can anyone provide guidance on setting up multicast
          >>>
          >>address
          >>
          >>>on Solaris 2.6?
          >>>
          >>>Bewildered,
          >>> Dan
          >>>
          >>
          >

SBS 2011 - Need to change Machine name and IP address range

We had upgraded to SBS 2011 and new hardware 6 months ago, we have recently been aquired by a larger company and want us to comply with their machine naming conventions and change the IP address range to fit in with their corporate structure. They
will be supplying us with a 2011/2012 Domain controller, this is to be added to our existing network as the primary DC supplying DNS, DHCP, WSUS
We use our SBS box for DNS, DHCP, Exchange, File server, Print server
How difficult is this going to be? Is it actually possible, or do we need to wipe the SBS box and install from scratch?Any help on this matter would be appreciated

As said, you can't change the name of the server or the domain, but you can change the IP addresses.
The bad news is that you can't integrate SBS to a larger corporate network. SBS needs to be at the root domain of the forest and hold all FSMO roles, and it can't have any trusts.
If the corporate wants to bring in a DC of their own AD domain and wants all clients to be joined to that domain, you just can't use SBS anymore, it won't fit in. You need to inform your corporate IT about the situation, and you need to make a new plan.
You will need some kind of migration from SBS to standard products first before you can join to the corporate network structure.
Tero Leskinen - MVP (Windows Server for Small and Medium Business / SBS)

Changing the multicast Address and Port giving error

I am using Coherence 3.3.1 jar files (Coherence.jar and tangosol.jar) in my local application. But when I try to change the multicast Address and Port in tangosole-coherence.xml(in Coherence.jar) then it is giving this error -
"This member could not join the cluster because of an incompatibility between the cluster protocol used by this member and the one being used by the rest of the cluster. This is most likely caused by a Coherence version mismatch, or by mismatched protocol filters (e.g. compression, or encryption)"
If i am using unique IP and Port then how can it be in a Cluster as this error stating. Please reply ASAP.

Hi,
There is a good chance that there is already the IP and port is being used by another cluster (which uses different versions of jars or configurations) and hence, when you are starting your cluster, throwing the error.
Can you double check if another cluster is already using it or not ?
Thanks,
Amit

Multicast Address

Hi,
Please tell us the use of multicast address while setting up cluster.
We had a network outage, and we were asked to restart weblogic servers (admin and managed server). When we restarted the application we found following error message in the log and the server start up status in admin console was showing "Server Failed to start properly". However we were able to open up our application GUI and work on it.
Thanks

Weblogic servers in cluster communicate among one another about their health using 2 ways - Multicast or unicast.
Multicast is a network protocol wherein a simple message is broadcast to a IP:port and any other process listening to this IP port receives it.
When you configure a weblogic cluster this way, the managed servers send a multicast message periodically about its state, and all other managed servers in the cluster configured to listen to the same multicast IP:port receives it. Note that the multicast message sender receives messages from others as well as its own message.
If no message is received from other members of a cluster then the server runs in independent mode, ie its not part of the cluster anymore. Hence failover wont happen. It will still continue to receive requests and serve them.
Hope this clarifies.

IPTV Multicast address range

Similar Messages

Maybe you are looking for