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.

Similar Messages

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

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
 >>>
 >>
 >

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 inside a solaris zone buggy ?

I need to post to a multicast address from within a solaris 10 (06.06) zone but the routing is abnormal:
On the global:
224.0.0.0 240.0.0.0 172.16.248.42 e1000g0 1500* 0 1 U 0 0
Inside the zone:
224.0.0.0 240.0.0.0 172.16.0.60 e1000g32001:1 1500* 0 1 U 0 0
As you can see the route is attached to a different interface which is strange cause the zone also inherit an access to e1000g0:
Any ideas cause the only solution I know is to change the multicast route but this is not possible inside a zone ...
route -n delete -interface 224.0/4 -gateway 172.16.0.60
delete net 224.0/4: gateway 172.16.0.60: insufficient privileges ....
Thanks

The zone attach the multicast to the 1st interface, which means for a zone:
I've changed the order in /etc/zones/myzone.xml
<network address="172.16.248.86" physical="e1000g0"/>
<network address="172.16.0.61" physical="e1000g32001"/>
<network address="172.16.244.86" physical="e1000g244001"/>
Now the route for the multicast is bounded to the correct interface:
224.0.0.0 240.0.0.0 172.16.248.43 e1000g0 1500* 0 1 U 0 0
As the global zone.

Redundant MOH Server and multicast addressing

Per SRND:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_chapter09186a00806e8c28.html#wp1043768
I want to use the 2nd method:
"Configure separate media resource groups (MRGs) for the same MoH server, with one MRG configured to use multicast for audio streams and the second MRG configured to use unicast. "
as well as use redundancy. My questions is:
Can I use the same multicast address (ie 239.1.1.1) for primary and backup moh server or do I need to put in a 2nd multicast address (ie 239.1.1.2) on the backup MOH server.
Thanks

Maybe for second Multicast MOH server, start at 239.1.10.1 or like 239.1.1.50.
Sankar is right, but if you add multiple audio source files and have like 4 multicast audio sources then it may start higher up for the audio source you are using.
In my time working on fixing systems I've seen people don't maintain/delete old audio sources so starting second MOH server at 239.1.1.11 could cause problems/conflicts potentially.
It would also be nice if they displayed the mcast address used for each audio source in CCMadmin so admins could see it easily without having to figure it out. Or for people who aren't aware of how the addresses increment per codec/audio source.

Multicast Addressing Scheme

Hi,
I've been asked to implement a Multicast addressing scheme for the University i am currently working at and would be grateful if someone could confirm my thinking as i haven't done a lot with Multicast before.
We have 6 main sites at the University that are currenrtly being moved over to a 10.* based addressing scheme with /12 masks:
site 1 - 10.16.0.0 /12
site 2 - 10.32.0.0 /12 etc...
Looking at the Multicast addressing RFC 2365, it would appear that local Multicast addressing needs to be allocated from 239.192.0.0 255.252.0.0 so i am thinking of taking the second octet of the 10.* scheme and using it in the 3rd of the Multicast scheme so we have some kind of addressing structure and allocating the Multicast addressing with /12 masks as follows:
site 1 = 239.192.16.0 /20
site 2 = 239.192.32.0 /20 etc..
Am i on the right track here?
TIA
Paddy

Salman,
Firstly many thanks for the information.
As usual, this leads me on to further questions about implementing multicast in our routed environment :)
As mentioned previously we have 6 main sites on the network, which are connected together using 100 Mbps LAN Extension circuits, they are not in a full mesh but each site is connected to two others so there is some kind of resilience. There are also smaller satellite sites connecting into each of the main sites using WAN links from 2 Mbps serial connections up to 10 Mbps LAN extensions.
As the multicast addressing scheme is going to be based loosely on the 10.* scheme and we will be using sparse mode I am thinking of manually configuring rendezvous points at each major site so all local site multicast traffic (from the satellite sites to the main site) at each location is controlled at the major site router as this is more than likely where the servers supplying multicast services will be located, is this the correct way to go?
If we are using PIM on all the WAN links between all sites, my understanding is that clients at any site will be able to use multicast services from servers at any site as PIM will populate the multicast routing tables on all routers with PIM enabled interfaces, and IGMP will control the queries and reports from around the network populating the multicast groups wherever they reside in the network - does this sound correct?
Also is it best to use CGMP between the LAN and WAN, Ive read that its much less resource intensive than IGMP snooping, does the fact that we are using IGMP on the WAN which I believe is enabled by default when using PIM have any issues with using CGMP between the LAN and WAN?
We have some pretty old switches at some of the network campuses (1900's), these are all being replaced in the next 8 months or so with 3750's. It looks like the 1900's support CGMP, however when looking at the support matrix for multicast the 6000 series switches don't support CGMP and we will be looking to put these into our main sites at the network core. Does this mean that there is a move towards IGMP snooping over CGMP, can both be implemented at the same time. I think there is a push to get multicasting working here quickly so we might have to go with CGMP to start and then move over to IGMP snooping, any thoughts on this would be appreciated
TIA
Paddy

API method to query multicast address and port of a cluster

I am new to Tangosol and I'm looking to write a quick Java dashboard that will display current information on our cluster, such as the clustername and the multicast address and port that is being used. Looking at the API I've found the Cluster object and I'm able to get the memeberset and the clustername.But I have not been able to find a way to query the multicast address and port being used by the cluster.
 Any help or links would be appreciated.
 Thanks,
 Len

Hi Len,
 All this information could be retrieved via JMX. Please see this Wiki page. Detailed documentation about the semantics of all exposed attributes and method could be found in the Javadoc for the <a href ="http://tinyurl.com/r75sy">Registry interface</a>.
 Regards,
 Gene

RTPManager initializing with multicast address!

Hi every body..
i use RTPManager and initializes it to multicastAddress and then in
addTarget() call i again pass same IP multicast address on two RTPManagers running on different machines.... but y dont i get NewParticipantEvent on any of the two PC`s ???
i did this i.e use same Multicasting address for initializing and addTraget(), cause JMF docs says it..
but... if i initializes to localAddress.. then things seems to work fine.. thats another question y is this so ??
i thing i am using 224.0.0.1 as a multicasting address in my LAN!
any body have a clue abt it??
Thanks in advance
bye

up

Setting listenPort, multicast address, etc. on command line

Weblogic version 6, Unix
I'm going to ask this question again, because it was apparently so hard, no
one could answer it. Is it possible to set the listenPort, cluster multicast
address, etc, on the command line? You could easily do this in version 5.1.
This is important because I have a set of start up scripts that I use that
select the listen port, cluster multicast address, etc. These scripts are
generic enough to allow multiple instances of weblogic. If this happens,
obviously the listen port, multicast address, etc. should not conflict. I
don't want to set these through the admin console.
Scott

I have j2sdk 1.4.2 i think the above link talks about methods supported by 1.5.Any other suggestions

ACE FT Multicast Address

Hello,
does anyone know the multicast address which the ace use to sync the
connection entries over his ft vlan ?
Greeting
Ed

ACE will use unicast ip address and broadcast mac-address.
Gilles.

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

Multicast address problems

In the start up scripts for my cluster nodes, I set
 weblogic.system.multicastAddress=224.1.1.100, the address setup by my IT
 group.
 When I start the cluster node, I see the following lines in the log:
 Mon May 15 10:16:05 PDT 2000: <System Props>
 weblogic.system.multicastAddress = 224.1.1.100
 . <other stuff>
 Mon May 15 10:16:06 PDT 2000: <WebLogicServer> Using default cluster
 multicast address 237.0.0.1
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 =========================================================
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer> = Joined cluster
 cluster_1 at address 237.0.0.1
 Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 =========================================================
 Why is weblogic joining the cluster at address 237.0.0.1 when I
 specified 224.1.1.100?
 In terms of the resulting behavior, jsp page requests to the proxy
 server are passed to the single cluster node and a page is generated
 without error. As soon as I add another cluster node to the cluster,
 requests that form a new session never send a response. I suspect that
 the cluster nodes are having trouble replicating the session.
 Any help?
 - Kevin


Thanks, this causes the nodes to join at the desired address.
 I am still seeing, however, that the jsp pages I want work file when
 there is one node in the cluster but hang forever when there are more
 than one nodes. The MulticastTest utility runs successfully. Can you
 suggest any other debugging options?
 - Kevin
 Prasad Peddada wrote:
 >
 > The property is weblogic.cluster.multicastAddress.
 >
 > - Prasad
 >
 > Andrew Park wrote:
 >
 > > i had a similar problem, but it was all caused by a typo in my java command
 > > line, where i set the multicast address. please double check...
 > >
 > > there is also the utils.MulticastTest utility. please refer to
 > > http://www.weblogic.com/docs51/techstart/utils.html
 > >
 > > andrew
 > >
 > > Kevin McEntee wrote in message <[email protected]>...
 > > >In the start up scripts for my cluster nodes, I set
 > > >weblogic.system.multicastAddress=224.1.1.100, the address setup by my IT
 > > >group.
 > > >
 > > >When I start the cluster node, I see the following lines in the log:
 > > >
 > > >Mon May 15 10:16:05 PDT 2000: <System Props>
 > > >weblogic.system.multicastAddress = 224.1.1.100
 > > >.
 > > >. <other stuff>
 > > >.
 > > >Mon May 15 10:16:06 PDT 2000: <WebLogicServer> Using default cluster
 > > >multicast address 237.0.0.1
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 > > >=========================================================
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer> = Joined cluster
 > > >cluster_1 at address 237.0.0.1
 > > >Mon May 15 10:16:07 PDT 2000: <WebLogicServer>
 > > >=========================================================
 > > >
 > > >Why is weblogic joining the cluster at address 237.0.0.1 when I
 > > >specified 224.1.1.100?
 > > >
 > > >In terms of the resulting behavior, jsp page requests to the proxy
 > > >server are passed to the single cluster node and a page is generated
 > > >without error. As soon as I add another cluster node to the cluster,
 > > >requests that form a new session never send a response. I suspect that
 > > >the cluster nodes are having trouble replicating the session.
 > > >
 > > >Any help?
 > > >
 > > >- Kevin

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

HELP! can't create multicast address on HPUX 11i

 Platform: HPUX 11i; weblogic 7.0.1
 I have installed a weblogic Admin Server and two weblogic managed servers on
 one HP server. They were all using one NIC who has three ip addresses with it.
 The multicast address I defined was 237.0.0.19 and it has never been used.
 I start the admin server ,that's ok. But when I start managed server,It's says:
 Starting Cluster Service...
 <Nov 28, 2002 6:19:41 PM GMT+08:00> <Error> <Cluster> <000116> <Failed to join
 cluster mycluster at address 237.0.0.19 due to : java.net.SocketException: error
 setting options
 java.net.SocketException: error setting options
 But when I configure a managed server on another machine whose OS was Linux,It
 can join the group.
 Why does it happen? Is it the problem generated by HPUX?


Did you try the MulticastTest in the weblogic Java Utilities to conform
 that that address is availble and works?
 In addition, are there any routers in the net that would prevent the
 multicast message from being propagated?
 I would try other address just to see if they work.
 lumin wrote:
 >
 > Platform: HPUX 11i; weblogic 7.0.1
 > I have installed a weblogic Admin Server and two weblogic managed servers on
 > one HP server. They were all using one NIC who has three ip addresses with it.
 > The multicast address I defined was 237.0.0.19 and it has never been used.
 > I start the admin server ,that's ok. But when I start managed server,It's says:
 >
 > Starting Cluster Service...
 > <Nov 28, 2002 6:19:41 PM GMT+08:00> <Error> <Cluster> <000116> <Failed to join
 > cluster mycluster at address 237.0.0.19 due to : java.net.SocketException: error
 > setting options
 > java.net.SocketException: error setting options
 > ..
 >
 > But when I configure a managed server on another machine whose OS was Linux,It
 > can join the group.
 >
 > Why does it happen? Is it the problem generated by HPUX?

Multicast Address

Similar Messages

Maybe you are looking for