Multicast group 224.0.1.40 !

I came by in a forum and this question really attracted me, my topology is completely based on dense mode, then why the routers join this group by default, if they dont will the topology will ever run into any problem if in future sparse mode is configured ?

Hi,
AFAIK the 224.0.1.40 is a reserved multicast group for cisco's Rp descovery. All cisco routers are members of this grup by default and listen to this group for Cisco RP discovery messages advertised by mapping agent even if it is not configured.I dont think there would be any problems if you change your topology to Sparse mode. But you should take in to account all the pros and cons.
HTH,
regards,
Shri :)

Similar Messages

Routed access design to support up to 2500 multicast groups

Hi all,
I'm doing routed access design with following:
- Routing protocol is OSPF.
- 3 layers with: Core/Distribution/Access design.
- Core: Catalyst 6500E Sup 2T.
- Distribution: ME 3800X / Catalyst 4500X.
- Access: ME 3400E.
We enable PIM from Core to Access layer.
At the moment, there are around 1000 multicast group in the network.
Cisco hardware limitation of multicast:
- Cisco ME 3400E can only support up to 1000 IGMP groups and multicast routes.
- Cisco ME 3800X can only support up to 2000 IGMP group and multicast routes with Metro IP Services license.
- Cisco Catalyst 4500X support up to 32K multicast routes.
- Cisco Catalyst 6500E Sup 2T support up to 128K multicast routes.
Requirement:
Design the network to support up to 2500 multicast groups.
So, are there any fine-tune in the design to meet above requirement?
Or I have to change access layer switch to higher model? (ex: 4500E)
Thanks,

hi there
replacing the hardware is one option
but the question here why are you going with routed access layer and in your case you have large Mcast routing table that going to be everywhere !!
have you considered using Cat65k or 45K in the distribution in VSS and use L2 from access to distribution
in this case you need to concern about the distribution routing table size and also VSS simplify the topology and managerially of the network rather than have it with a complicated routing design
routed access is a good and recommend as well for quicker convergence time and no reliance on STP or HSRP/VRRP timers
however it could comlicate the routing design !
while VSS will also eliminate the reliance on HSRP/VRRP and STP with more added simplicity to the topology and design
so you may go with 45K VSS in the distribution and 65K with VSS in the core as well and in the access using L2 uplinks to the distribution and the uplinks everywhere can use multi-chassis etherchannel MEC, for increased network capacity in terms of bandwidth and quicker convergence time in the case of a link failure as well, Plus you will be able to support the desired Mcast routing table in the distribution and Core !!
hope this help

SNMP query for multicast group count

I want to get the total number of multicast groups on a switch. Is there an oid that will give me the info (ie. the number that's given by "show ip igmp snooping groups count")? If there is no oid, is there a way query the groups (show ip igmp snooping groups)? I'm thinking with the 2nd option I might be able to count the number of entries returned by an snmpwalk or something and turn that into a number.
Right now i'm logging into the switch with a script and running the command but that might be a problem with all those logins (only every 5 minutes though) so I'd like to do this via SNMP if possible.
Any ideas?
Thanks

Works just fine!!!
Thanks!
LA$$E
Hi,
Well, at the very least, you can create a formula
column in your break group using a combination of the
same where clause as your original query and the
break values for the group so that you are getting
the correct records. If you have it in the break
group, then it will execute for each record in that
group.
Hope that helps,
Toby

Maximum number of multicast groups on a given port?

Using linux (Ubuntu 8.4 with jdk 1.6.10 and 1.5.12) if I try to join more than 20 groups to a MulticastSocket open on a given port I get the following exception:
FINE 14:45:45.883:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.0.1.118
FINE 14:45:45.883:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.12.1.113
FINE 14:45:45.884:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.20.0.43
FINE 14:45:45.884:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.0.0.42
FINE 14:45:45.884:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.115.246.43
FINE 14:45:45.885:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.125.246.43
FINE 14:45:45.885:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.125.246.75
FINE 14:45:45.885:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.12.1.120
FINE 14:45:45.885:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.215.246.45
FINE 14:45:45.886:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.12.0.43
FINE 14:45:45.886:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.125.246.20
FINE 14:45:45.886:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.1.1.120
FINE 14:45:45.887:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.12.1.118
FINE 14:45:45.887:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.115.246.42
FINE 14:45:45.887:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.115.246.20
FINE 14:45:45.888:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /233.215.246.47
FINE 14:45:45.888:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.12.1.112
FINE 14:45:45.888:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.1.0.43
FINE 14:45:45.888:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.1.1.118
FINE 14:45:45.889:net.c4i.socketcomms.MulticastSocketListener.bind 10: Adding Mcast Group: /226.1.0.75
WARNING 14:45:45.889:net.c4i.socketcomms.MulticastSocketListener.bind 10: Could not join multicast group /233.15.246.43
java.net.SocketException: No buffer space available
java.net.PlainDatagramSocketImpl.join(Native Method)
java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
net.c4i.socketcomms.MulticastSocketListener.bind(MulticastSocketListener.java:143)
net.c4i.socketcomms.MulticastProtocolManager.createListener(MulticastProtocolManager.java:154)
net.c4i.socketcomms.MulticastProtocolManager.<init>(MulticastProtocolManager.java:100)
net.c4i.socketcomms.MulticastProtocolManager.getInstance(MulticastProtocolManager.java:67)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
net.c4i.socketcomms.SocketManager.createProtocol(SocketManager.java:245)
net.c4i.socketcomms.SocketManager.<init>(SocketManager.java:157)
net.c4i.socketcomms.SocketManager.getInstance(SocketManager.java:116)
net.c4i.infrastructure.C4IAdapterManager.<init>(C4IAdapterManager.java:172)
net.c4i.infrastructure.C4IAdapterManager.getInstance(C4IAdapterManager.java:263)
net.c4i.infrastructure.C4IAdapterManager.launch(C4IAdapterManager.java:492)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
Is there any known way to workaround this issue? I've searched but have not seen any similar issues. I also cannot reduce the number of multicast groups in use as I have no control of that.
Noah

Is there any known way to workaround this issue?It may be a tunable kernel parameter, and you may be able to tweak it somehow, but that would be a Linux question, not a Java question.
I also cannot reduce the number of multicast groups in use as I have no control of that.You may not have any choice. If the kernel will only give you 20, bad luck.

Join multicast group on AIR DatagramSocket ?

Hello Adobe experts,
I'm currently testing Flex/AIR for a new software that we have to design to display data received from the network and I'm very excited about all possibilities Flash offers in terms of UI and how easy it is to quickly develop a nice-looking, portable application, compared to other technologies (like Java, though richer in terms of API but harder to write code reusable for desktop, Internet and mobile apps, and not so good looking ).
The application itself gets data from a multicast group and formats it on the screen (images, graphs, ...).
So I'm really willing to use Flash to build this app and after a few benchmarking/prototyping I'm using a DatagramSocket (AIR-only, that's fine) to read UDP datagrams and it's working fine except for two tiny things on which I couldn't find any answer:
I can't have the socket join a multicast group
I can't set the send/receive buffer size for the socket
I have a lot of code in C and Java for that and both are just a single call to "setsockopt" function:
In C:
setsockopt(sock, IPPROTO_IP, IP_ADD_MEMBERSHIP, &group, sizeof(struct ip_mreq)) - where "group" describe the multicast group to join
setsockopt(sock, SOL_SOCKET, SO_RCVBUF, &sz, sizeof(sz)) - where "sz" is the number of byte to use for the receive buffer
In Java it's even simpler, using a MulticastSocket:
sock.joinGroup(group)
sock.setReceiveBufferSize(sz)
I tried to use Alchemy to write simple functions to create an UDP socket and have it join a multicast group but alas, the "socket" call returns -1, as it seems that sockets cannot be created in Alchemy environment (though compilation works without problem...).
I find it hard to believe that I'm the only one needing these two tiny "setsockopt" calls... I found on Adobe forums people trying to set the TCP_NODELAY option on a socket (also using setsockopt in the end) but without success...
By the way, the data come from an electronic board and is somehow coded in VHDL so I can't use RTMFP on that, though it seems to implement the functionnalities I need (or at least the multicast group part, the receive buffer size would be a bonus).
Well, I'm rather disapointed by this as Flash fills remarkably 99.9% of the application needs but this tiny 0.1% makes it impossible for it to get the data, thus making it useless...
And we don't want that I turn to Silverlight, do we?
Thank you all for any help and answers on this topic!
Matthieu

Thanks, that's what I was planning to do but in C or Java (everyone has its favorites right? ): use another program as a kind of "proxy" to redirect the multicast streams to local unicast AIR sockets...
But I'd rather have a nice API modification from Adobe on that matter. This kind of proxy is clearly "hacking" your way out of an API miss. You also have to make sure that your "proxy" is running on the local machine.
It's not as if multicast was a new technology or something nobody uses... It's standard and it's simple when you can already handle UDP sockets so I don't know why they don't want to implement these 10 lines of code...
Anyway, thank you for your answer, I'll stick to something similar (but I'll do Java ).
Matthieu

RTPManager: problem joining multicast group

We've written an application that sends and receives audio and video streams over RTP to a multicast group. If two of these applications are both running on the LAN, it works fine (our router is multicast-enabled). If one application (A) is running on the LAN, and another (B) is running remote and connected to the LAN via VPN, then A receives B's audio and video, but B sometimes doesn't receive A's audio and video. If another application (C) is added on the LAN, C behaves just like A - C receives audio and video from both A and B, but B still doesn't see either A or C.
On some occasions, rebooting B and re-establishing the VPN connection fixes the problem, and on other occasions, this doesn't change the behavior at all.
Using Ethereal, we've confirmed that B doesn't receive any of the traffic from the multicast group, even though its successfully sending traffic to that group. Further research revealed that, on B, the IGMP join requests were being sent to B's normal network interface, and NOT to the VPN network interface. However, all the RTP and RTCP traffic was being sent to the VPN network interface.
Does anyone know how to control (or at least affect) which network interface is used by RTPManager when joining the multicast group? I'm not sure if this problem is a result of RTPManager, of the NIC driver, or something else. I think one option is to write an RTPConnector implementation that handles all the transmission and reception manually, but I hope there's a better, easier option. Thanks for any help.

Hi Eric,
I am doing exactly the same thing. I have the video running fine, and I am relying on VPN connection for remote monitoring of the video. My setup is a little more complicated - I am running a setup/start/stop/teardown session manager (like rtsp) and also a keep alive listener (like rtcp) for each user.
I have one little annoyance which is stoppping me from testing this over the VPN, on my remote machiens I get a startup error:
11:40:13.4 request = control_start
11:40:15.1 Video transmitted as:
11:40:15.1   JPEG/RTP, 320x240, FrameRate=15.0
Failed to realize: com.sun.media.ProcessEngine@7cbde6
Cannot build a flow graph with the customized options:
    Unable to transcode format: RGB, 320x240, FrameRate=15.0, Length=230400, 24-
bit, Masks=3:2:1, PixelStride=3, LineStride=960, Flipped
      to: JPEG/RTP, 320x240, FrameRate=15.0
      outputting to: RAW/RTP
Error: Unable to realize com.sun.media.ProcessEngine@7cbde6
11:40:16.1 response = 500I have run a debug on the two networks, the multicast runs fine on my machine, and the processor is realized, and the cameras have identical traces looping over the supported formats. Is this purely a format issue or could this be a router not configured for multicast?
Do you (or anyone!) have an idea about this? The program works on my setup of camera etc, and on a clone machine, with diff cameras (but the same if you know what I mean) it fails...
I'll let you know if I solve the VPN problem (after I fix this) I watched this topic.

NDP - Solicited node multicast group

Hello everyone,
I can`t understand the process of layer3 to layer2 address resolution in IPv6.
In order to make a Layer-2 (eg. Ethernet) delivery, it needs to know the target host's hardware address (eg. "Ethernet MAC address"). But in order to do this, it must first determine which hardware address to send it to. To do this, an IPv6 host will construct the Solicited-node Multicast Address related to the target address.
The IPv6 solicited-node multicast address has the prefix FF02:0:0:0:0:1:FF00:0000/104 concatenated with the 24 low-order bits of a corresponding IPv6 address.
For the target with address
fe80::2aa:ff:fe28:9c5a
solicated node multicast address would become
ff02::1:ff28:9c5a.
1- For example when a host has two unicast address 2001::AB:CDEA and link local fe80:2aa:ff:fe28:9c5a on its interface, does it join the associated solicited-node multicast group for every address to which it is assigned or only for link local adress?.
2- If only for link local address, how will the source device know the link local address of target to borrow last 24 bit? Can I use global address for target address while layer3 to layer2 address resolution?
3- Does all ND functions use link local address? Must a node know all neighbours link local address? If yes, what mechanism are needed to learn link local address of neighbours.
All replies will be appreciated.
Thanks
Gokmen...

Hi,
1) a node always joins the sollicited-node multicast for every IPv6 address it has configured on the ethernet interface including the link-local.
2) this destination multicast address is used for neighbour sollicitation( equivalent of ARP in IPv4) and DAD( duplicate address detection) which is the equivalent of Gratuitous ARP request in IPv4.
So when you want to communicate with a destination IPv6 address it must first do a NS to find out the L2 address and it will send it to the sollicited-node multicast corresponding to the IPv6 destination address
when the node is configured with an IPv6 address it will verify if it is unique by sending a NS to its sollicited-node multicast and if it receives a reply it considers the address is not unique.
3) no it must know how to send to link-local if it wants to communicate with link-local only
http://www.ietf.org/rfc/rfc2461.txt
Regards.
Alain

Multicast group capacity

We are using 3560 and 3750 PoE switches in a network which
interconnects a lot of clients (WIN XP professional) using a proprietary VoIP software
solution.
This Software uses Multicast groups for communication and now we are
running into the limitation of 1000 multicast groups supported by these
switches.
Does anybody know if there is any possibility to extend the maximum
number of Multicast groups on the 3560 and 3750 Cisco switches? IOS
update? Memory extension?
Thanks in advance

Hi,
Currently, we support only 1024 multicast routes+IGMP groups.
To extend the maximum number, we need code changes.
At the moment, no code changes planned.
Tom.

Can iAS multicast group cross clusters & machines

Say I have 2 clusters C1 & C2 deployed on different machines. Each cluster has 2 iAS instances. All components have Sticky flag.
Now I have 2 web servers iWS1 & iWS2 (on separate machines too).
A load balancer distributes requests between web servers using server affinity rule.
I would like the following to happen and am not sure of the settings that must be made
1) User1 comes through iWS1 and sets up a session on C1.
2) Subsequent requests from user1 will follow the same path because of server affinity at LoadBalance level and stickiness at web connector level.
3) If iWS1 is brought down, Load balancer would be forced to send User1 requests to iWS2. I would like iWS2 to start forwarding user1 requests to C1.
Also, it would be great if in some way, iWS2 could send any new users without existing session to C2 only. This would allow me to bleed users of C1 to perform an upgrade.
Thanks
GN

If C1 and C2 share the same ldap, then both the webservers will be able to forward requests to both the clusters (provided the application is deployed on all the servers). This is one solution to the problem.
Another solution, which is probably a hack is that you manually put the IP address of all the servers under the GUID of the application to be distributed.
This will allow the webserver to forward requests to any of the servers in C1 and C2.
In fact this method can be used to load balance even across clusters/multicast groups.
Make sure you make the load balancing option as web connector driven.
Note that the Multicast group doesn't come into picture while load balancing. You might see a number of iAS servers registered under \\6.5\GMS, but the webconnector doesn't forward requests to them unless they are also registered under the application GUID.
If you want that W2(webserver of C2) should forward requests to C1 only if W1 is down, then I don't know how to do that.
Also I don't know how to make sure that W2 should forward requests from all the new users only to C2 in that case.
-harjit

Slm2005 not leaving multicast group

Hi,
I have this SML2005 smart switch I try to use surf over some video multicast group. I have 2 video sources streaming on different multicast addresses, and 1 video receiver with a single channel. All are connected directly to the switch.
When I toggle between both sources on the receiver end, I clearly see the igmp group leave for the address of the previous channel and the igmp report for the new address on the latest channel. This is observed while setting a port of the switch in mirror and capturing the ethernet traffic. So far so good.
What I observe is the the switch continues to send the stream of the previous channel to the receiver, even though there was an explicit igmp group leave.
The switch is configured as follow:
global:
-enable igmp snooping: on
-Enable Unregistered IP Multicast Flooding: off
vlan 1:
-enable igmp snooping: on
-Enable IGMP Querying: on
I expected some latency leave, but I let this run for 20minutes with the unwanted stream continuously being sent to the receiver.
What this causes is when both stream are present, the port of the receiver may exceed the allowed bandwidth and some packets are dropped.
Any help would be appreciated.
--Martin

Hi and welcome to the Skype Community,
You can leave a group chat any time without compromising any of the separate conversation history or 1-on-1 conversation with the contact who originally invited you to the group. Take a look at our article on group chats explaining its features:
https://support.skype.com/en/faq/FA1005/how-do-i-start-a-group-instant-message-in-skype-for-windows-...
P.S.: Just out of curiosity: When you open the Windows discussion board do you see the big green "New Topic" button on top:
If not do you see any other button at that location?
Follow the latest Skype Community News
↓ Did my reply answer your question? Accept it as a solution to help others, Thanks. ↓

Dual network interface when joining multicast group

Hello,
I've have a machine with two networks interfaces, eth0 and eth1. The route table is configured to send all the multicast traffic through eth1.
This is
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth1
I have the following code that joins to a multicast address to listen incoming messages in my Java application
InetAddress group = InetAddress.getByName(multiCastAddress);
socket = new MulticastSocket(Integer.parseInt(multiCastPort));
socket.joinGroup(group);
The result is that the application can not see the multicast traffic since the joinGroup operation is always done on eth0, guess because JVM selects the first one available.
If I change the route entry to use eth0 for all the multicast traffic, the same code works perfectly, and from my Java application I can see the multicast traffic.
This is
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0
Is there any way to force to join a specific network interface?
Thanks

The answer is staring you in the face in the Javadoc:
http://java.sun.com/j2se/1.5.0/docs/api/java/net/MulticastSocket.html#joinGroup(java.net.SocketAddress,%20java.net.NetworkInterface)
That bug report only concerns setNetworkInterface(), which the OP isn't using, on Linux and IPv6, and it's dated 2002.

Multicast Group Questions

If I have 10 multicast streams going to flash media server how should I configure Group name and stream names ? Each stream will be watched by a different set of people but pushed to same FMS . Should giving each stream a seperate name and seperate stream name will be fine ?
Thanks

It depends on how do you want to implement. You can have different streams under one NetGroup or you can create one NetGroup for one set of people.

Redundent cotrllers multicasting

hello friends,
if we have 2 cisco 2504 series wlcs and use multicast fetures in both and both are primary and secondry for LAPs
what about of we use multicast ip address let's say 255.239.1.60 can we use the same ip address for the secondry contrller too or we should use any other ip ?
thanks

If Primary got 230.0.0.1 then use 230.0.0.2 for secondary WLC.
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70ccfg.html#wp1089006
Guidelines for Using Multicast Mode
Follow these guidelines when you enable multicast mode on your network:
•The Cisco Unified Wireless Network solution uses some IP address ranges for specific purposes, and you should keep these ranges in mind when configuring a multicast group:
–224.0.0.0 through 224.0.0.255—Reserved link local addresses
–224.0.1.0 through 238.255.255.255—Globally scoped addresses
–239.0.0.0 through 239.255.x.y /16—Limited scope addresses
•The CAPWAP multicast group configured on the controllers should be different for different controllers.

Route IGMP link-local groups

There are two VLANs in network:
VLAN 30: 192.168.1.0/24
VLAN 40: 192.168.2.0/24
A IGMP multicast group 224.0.0.251 is used for devices in both VLANs.
I try to configure the router to enable the multicast routing, but it seems the router cannot join that multicast group:
ip multicast-routing distributed
3560g-client(config-if)#ip igmp join-group 224.0.0.251
Illegal multicast group address
So is there anyway to make that multicast group routable?
Thank you.

The multicast address, you are trying to join is a link-local multicast address and does not follow normal procedures of join. Any multicast address which belongs to 224.0.0.x is link-local address and few are reserved for protocols which runs over a link, like 224.0.0.9 is used for RIP and 224.0.0.10 is for EIGRP. and similarly 224.0.0.251 is used of mDNS. We will same error message for all these groups.
R6_ASR6(config-if)#ip igmp join-group 224.0.0.9
Illegal multicast group address
R6_ASR6(config-if)#ip igmp join-group 224.0.0.10
Illegal multicast group address
R6_ASR6(config-if)#
http://en.wikipedia.org/wiki/Multicast_address
http://en.wikipedia.org/wiki/Multicast_DNS
--- Please don't forget to rate helpful posts -----
Regards,
Akash

Failed preliminary checks for Oracle Real Application Cluster 12C.

Hi, all. Please, help to investigate and solve. Thanks.
[grid@orac1 grid]$ ./runcluvfy.sh stage -pre crsinst -n orac1,orac2 -fixup -verbose
Performing pre-checks for cluster services setup
Checking node reachability...
Check: Node reachability from node "orac1"
Destination Node                      Reachable?
orac1                                 yes
orac2                                 yes
Result: Node reachability check passed from node "orac1"
Checking user equivalence...
Check: User equivalence for user "grid"
Node Name                             Status
orac2                                 passed
orac1                                 passed
Result: User equivalence check passed for user "grid"
Checking node connectivity...
Checking hosts config file...
Node Name                             Status
orac1                                 passed
orac2                                 passed
Verification of the hosts config file successful
Interface information for node "orac1"
Name   IP Address      Subnet          Gateway         Def. Gateway    HW Address        MTU
eth0   10.154.137.101 10.154.137.0    0.0.0.0         10.0.4.2        08:00:27:28:D1:1F 1500
eth1   10.154.138.101 10.154.138.0    0.0.0.0         10.0.4.2        08:00:27:51:E8:B9 1500
eth2   10.0.4.15       10.0.4.0        0.0.0.0         10.0.4.2        08:00:27:5B:D7:29 1500
Interface information for node "orac2"
Name   IP Address      Subnet          Gateway         Def. Gateway    HW Address        MTU
eth0   10.154.137.102 10.154.137.0    0.0.0.0         10.0.4.2        08:00:27:7F:C8:70 1500
eth1   10.154.138.102 10.154.138.0    0.0.0.0         10.0.4.2        08:00:27:9D:27:D8 1500
eth2   10.0.4.15       10.0.4.0        0.0.0.0         10.0.4.2        08:00:27:6E:92:43 1500
Check: Node connectivity of subnet "10.154.137.0"
Source                          Destination                     Connected?
orac1[10.154.137.101]           orac2[10.154.137.102]           yes
Result: Node connectivity passed for subnet "10.154.137.0" with node(s) orac1,orac2
Check: TCP connectivity of subnet "10.154.137.0"
Source                          Destination                     Connected?
orac1:10.154.137.101            orac2:10.154.137.102            failed
ERROR:
PRVF-7617 : Node connectivity between "orac1 : 10.154.137.101" and "orac2 : 10.154.137.102" failed
Result: TCP connectivity check failed for subnet "10.154.137.0"
Check: Node connectivity of subnet "10.154.138.0"
Source                          Destination                     Connected?
orac1[10.154.138.101]           orac2[10.154.138.102]           yes
Result: Node connectivity passed for subnet "10.154.138.0" with node(s) orac1,orac2
Check: TCP connectivity of subnet "10.154.138.0"
Source                          Destination                     Connected?
orac1:10.154.138.101            orac2:10.154.138.102            failed
ERROR:
PRVF-7617 : Node connectivity between "orac1 : 10.154.138.101" and "orac2 : 10.154.138.102" failed
Result: TCP connectivity check failed for subnet "10.154.138.0"
Check: Node connectivity of subnet "10.0.4.0"
Source                          Destination                     Connected?
orac1[10.0.4.15]                orac2[10.0.4.15]                yes
Result: Node connectivity passed for subnet "10.0.4.0" with node(s) orac1,orac2
Check: TCP connectivity of subnet "10.0.4.0"
Source                          Destination                     Connected?
orac1:10.0.4.15                 orac2:10.0.4.15                 failed
ERROR:
PRVF-7617 : Node connectivity between "orac1 : 10.0.4.15" and "orac2 : 10.0.4.15" failed
Result: TCP connectivity check failed for subnet "10.0.4.0"
Interfaces found on subnet "10.0.4.0" that are likely candidates for VIP are:
orac1 eth2:10.0.4.15
orac2 eth2:10.0.4.15
WARNING:
Could not find a suitable set of interfaces for the private interconnect
Checking subnet mask consistency...
Subnet mask consistency check passed for subnet "10.154.137.0".
Subnet mask consistency check passed for subnet "10.154.138.0".
Subnet mask consistency check passed for subnet "10.0.4.0".
Subnet mask consistency check passed.
ERROR:
PRVG-1172 : The IP address "10.0.4.15" is on multiple interfaces "eth2,eth2" on nodes "orac2,orac1"
Result: Node connectivity check failed
Checking multicast communication...
Checking subnet "10.154.137.0" for multicast communication with multicast group "224.0.0.251"...
PRVG-11138 : Interface "10.154.137.101" on node "orac1" is not able to communicate with interface "10.154.137.101" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.137.101" on node "orac1" is not able to communicate with interface "10.154.137.102" on node "orac2" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.137.102" on node "orac2" is not able to communicate with interface "10.154.137.101" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.137.102" on node "orac2" is not able to communicate with interface "10.154.137.102" on node "orac2" over multicast group "224.0.0.251"
Checking subnet "10.154.138.0" for multicast communication with multicast group "224.0.0.251"...
PRVG-11138 : Interface "10.154.138.101" on node "orac1" is not able to communicate with interface "10.154.138.101" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.138.101" on node "orac1" is not able to communicate with interface "10.154.138.102" on node "orac2" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.138.102" on node "orac2" is not able to communicate with interface "10.154.138.101" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.154.138.102" on node "orac2" is not able to communicate with interface "10.154.138.102" on node "orac2" over multicast group "224.0.0.251"
Checking subnet "10.0.4.0" for multicast communication with multicast group "224.0.0.251"...
PRVG-11138 : Interface "10.0.4.15" on node "orac1" is not able to communicate with interface "10.0.4.15" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.0.4.15" on node "orac1" is not able to communicate with interface "10.0.4.15" on node "orac2" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.0.4.15" on node "orac2" is not able to communicate with interface "10.0.4.15" on node "orac1" over multicast group "224.0.0.251"
PRVG-11138 : Interface "10.0.4.15" on node "orac2" is not able to communicate with interface "10.0.4.15" on node "orac2" over multicast group "224.0.0.251"
Checking ASMLib configuration.
Node Name                             Status
orac1                                 passed
orac2                                 passed
Result: Check for ASMLib configuration passed.
Check: Total memory
Node Name     Available                 Required                  Status
orac2         5.714GB (5991520.0KB)     4GB (4194304.0KB)         passed
orac1         5.714GB (5991520.0KB)     4GB (4194304.0KB)         passed
Result: Total memory check passed
Check: Available memory
Node Name     Available                 Required                  Status
orac2         5.2293GB (5483324.0KB)    50MB (51200.0KB)          passed
orac1         5.1456GB (5395600.0KB)    50MB (51200.0KB)          passed
Result: Available memory check passed
Check: Swap space
Node Name     Available                 Required                  Status
orac2         6.125GB (6422520.0KB)     5.714GB (5991520.0KB)     passed
orac1         6.125GB (6422520.0KB)     5.714GB (5991520.0KB)     passed
Result: Swap space check passed
Check: Free disk space for "orac2:/usr,orac2:/var,orac2:/etc,orac2:/sbin,orac2:/tmp"
Path              Node Name     Mount point   Available     Required      Status
/usr              orac2         /             37.8398GB     1.0635GB      passed
/var              orac2         /             37.8398GB     1.0635GB      passed
/etc              orac2         /             37.8398GB     1.0635GB      passed
/sbin             orac2         /             37.8398GB     1.0635GB      passed
/tmp              orac2         /             37.8398GB     1.0635GB      passed
Result: Free disk space check passed for "orac2:/usr,orac2:/var,orac2:/etc,orac2:/sbin,orac2:/tmp"
Check: Free disk space for "orac1:/usr,orac1:/var,orac1:/etc,orac1:/sbin,orac1:/tmp"
Path              Node Name     Mount point   Available     Required      Status
/usr              orac1         /             32.4382GB     1.0635GB      passed
/var              orac1         /             32.4382GB     1.0635GB      passed
/etc              orac1         /             32.4382GB     1.0635GB      passed
/sbin             orac1         /             32.4382GB     1.0635GB      passed
/tmp              orac1         /             32.4382GB     1.0635GB      passed
Result: Free disk space check passed for "orac1:/usr,orac1:/var,orac1:/etc,orac1:/sbin,orac1:/tmp"
Check: User existence for "grid"
Node Name     Status                    Comment
orac2         passed                    exists(1100)
orac1         passed                    exists(1100)
Checking for multiple users with UID value 1100
Result: Check for multiple users with UID value 1100 passed
Result: User existence check passed for "grid"
Check: Group existence for "oinstall"
Node Name     Status                    Comment
orac2         passed                    exists
orac1         passed                    exists
Result: Group existence check passed for "oinstall"
Check: Group existence for "dba"
Node Name     Status                    Comment
orac2         passed                    exists
orac1         passed                    exists
Result: Group existence check passed for "dba"
Check: Membership of user "grid" in group "oinstall" [as Primary]
Node Name         User Exists   Group Exists User in Group Primary       Status
orac2             yes           yes           yes           yes           passed
orac1             yes           yes           yes           yes           passed
Result: Membership check for user "grid" in group "oinstall" [as Primary] passed
Check: Membership of user "grid" in group "dba"
Node Name         User Exists   Group Exists User in Group Status
orac2             yes           yes           yes           passed
orac1             yes           yes           yes           passed
Result: Membership check for user "grid" in group "dba" passed
Check: Run level
Node Name     run level                 Required                  Status
orac2         5                         3,5                       passed
orac1         5                         3,5                       passed
Result: Run level check passed
Check: Hard limits for "maximum open file descriptors"
Node Name         Type          Available     Required      Status
orac2             hard          4096          65536         failed
orac1             hard          4096          65536         failed
Result: Hard limits check failed for "maximum open file descriptors"
Check: Soft limits for "maximum open file descriptors"
Node Name         Type          Available     Required      Status
orac2             soft          1024          1024          passed
orac1             soft          4096          1024          passed
Result: Soft limits check passed for "maximum open file descriptors"
Check: Hard limits for "maximum user processes"
Node Name         Type          Available     Required      Status
orac2             hard          46654         16384         passed
orac1             hard          46654         16384         passed
Result: Hard limits check passed for "maximum user processes"
Check: Soft limits for "maximum user processes"
Node Name         Type          Available     Required      Status
orac2             soft          1024          2047          failed
orac1             soft          1024          2047          failed
Result: Soft limits check failed for "maximum user processes"
Check: System architecture
Node Name     Available                 Required                  Status
orac2         x86_64                    x86_64                    passed
orac1         x86_64                    x86_64                    passed
Result: System architecture check passed
Check: Kernel version
Node Name     Available                 Required                  Status
orac2         2.6.32-279.el6.x86_64     2.6.32                    passed
orac1         2.6.32-279.el6.x86_64     2.6.32                    passed
Result: Kernel version check passed
Check: Kernel parameter for "semmsl"
Node Name         Current       Configured    Required      Status        Comment
orac1             250           250           250           passed
orac2             250           250           250           passed
Result: Kernel parameter check passed for "semmsl"
Check: Kernel parameter for "semmns"
Node Name         Current       Configured    Required      Status        Comment
orac1             32000         32000         32000         passed
orac2             32000         32000         32000         passed
Result: Kernel parameter check passed for "semmns"
Check: Kernel parameter for "semopm"
Node Name         Current       Configured    Required      Status        Comment
orac1             100           100           100           passed
orac2             100           100           100           passed
Result: Kernel parameter check passed for "semopm"
Check: Kernel parameter for "semmni"
Node Name         Current       Configured    Required      Status        Comment
orac1             128           128           128           passed
orac2             128           128           128           passed
Result: Kernel parameter check passed for "semmni"
Check: Kernel parameter for "shmmax"
Node Name         Current       Configured    Required      Status        Comment
orac1             4398046511104 4398046511104 3067658240    passed
orac2             4398046511104 4398046511104 3067658240    passed
Result: Kernel parameter check passed for "shmmax"
Check: Kernel parameter for "shmmni"
Node Name         Current       Configured    Required      Status        Comment
orac1             4096          4096          4096          passed
orac2             4096          4096          4096          passed
Result: Kernel parameter check passed for "shmmni"
Check: Kernel parameter for "shmall"
Node Name         Current       Configured    Required      Status        Comment
orac1             4294967296    4294967296    599152        passed
orac2             4294967296    4294967296    599152        passed
Result: Kernel parameter check passed for "shmall"
Check: Kernel parameter for "file-max"
Node Name         Current       Configured    Required      Status        Comment
orac1             6815744       6815744       6815744       passed
orac2             6815744       6815744       6815744       passed
Result: Kernel parameter check passed for "file-max"
Check: Kernel parameter for "ip_local_port_range"
Node Name         Current       Configured    Required      Status        Comment
orac1             between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed
orac2             between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed
Result: Kernel parameter check passed for "ip_local_port_range"
Check: Kernel parameter for "rmem_default"
Node Name         Current       Configured    Required      Status        Comment
orac1             262144        262144        262144        passed
orac2             262144        262144        262144        passed
Result: Kernel parameter check passed for "rmem_default"
Check: Kernel parameter for "rmem_max"
Node Name         Current       Configured    Required      Status        Comment
orac1             4194304       4194304       4194304       passed
orac2             4194304       4194304       4194304       passed
Result: Kernel parameter check passed for "rmem_max"
Check: Kernel parameter for "wmem_default"
Node Name         Current       Configured    Required      Status        Comment
orac1             262144        262144        262144        passed
orac2             262144        262144        262144        passed
Result: Kernel parameter check passed for "wmem_default"
Check: Kernel parameter for "wmem_max"
Node Name         Current       Configured    Required      Status        Comment
orac1             1048576       1048576       1048576       passed
orac2             1048576       1048576       1048576       passed
Result: Kernel parameter check passed for "wmem_max"
Check: Kernel parameter for "aio-max-nr"
Node Name         Current       Configured    Required      Status        Comment
orac1             1048576       1048576       1048576       passed
orac2             1048576       1048576       1048576       passed
Result: Kernel parameter check passed for "aio-max-nr"
Check: Package existence for "binutils"
Node Name     Available                 Required                  Status
orac2         binutils-2.20.51.0.2-5.34.el6 binutils-2.20.51.0.2      passed
orac1         binutils-2.20.51.0.2-5.34.el6 binutils-2.20.51.0.2      passed
Result: Package existence check passed for "binutils"
Check: Package existence for "compat-libcap1"
Node Name     Available                 Required                  Status
orac2         compat-libcap1-1.10-1     compat-libcap1-1.10       passed
orac1         compat-libcap1-1.10-1     compat-libcap1-1.10       passed
Result: Package existence check passed for "compat-libcap1"
Check: Package existence for "compat-libstdc++-33(x86_64)"
Node Name     Available                 Required                  Status
orac2         compat-libstdc++-33(x86_64)-3.2.3-69.el6 compat-libstdc++-33(x86_64)-3.2.3 passed
orac1         compat-libstdc++-33(x86_64)-3.2.3-69.el6 compat-libstdc++-33(x86_64)-3.2.3 passed
Result: Package existence check passed for "compat-libstdc++-33(x86_64)"
Check: Package existence for "libgcc(x86_64)"
Node Name     Available                 Required                  Status
orac2         libgcc(x86_64)-4.4.7-11.el6 libgcc(x86_64)-4.4.4      passed
orac1         libgcc(x86_64)-4.4.7-11.el6 libgcc(x86_64)-4.4.4      passed
Result: Package existence check passed for "libgcc(x86_64)"
Check: Package existence for "libstdc++(x86_64)"
Node Name     Available                 Required                  Status
orac2         libstdc++(x86_64)-4.4.7-11.el6 libstdc++(x86_64)-4.4.4   passed
orac1         libstdc++(x86_64)-4.4.7-11.el6 libstdc++(x86_64)-4.4.4   passed
Result: Package existence check passed for "libstdc++(x86_64)"
Check: Package existence for "libstdc++-devel(x86_64)"
Node Name     Available                 Required                  Status
orac2         libstdc++-devel(x86_64)-4.4.7-11.el6 libstdc++-devel(x86_64)-4.4.4 passed
orac1         libstdc++-devel(x86_64)-4.4.7-11.el6 libstdc++-devel(x86_64)-4.4.4 passed
Result: Package existence check passed for "libstdc++-devel(x86_64)"
Check: Package existence for "sysstat"
Node Name     Available                 Required                  Status
orac2         sysstat-9.0.4-20.el6      sysstat-9.0.4             passed
orac1         sysstat-9.0.4-20.el6      sysstat-9.0.4             passed
Result: Package existence check passed for "sysstat"
Check: Package existence for "gcc"
Node Name     Available                 Required                  Status
orac2         gcc-4.4.7-11.el6          gcc-4.4.4                 passed
orac1         gcc-4.4.7-11.el6          gcc-4.4.4                 passed
Result: Package existence check passed for "gcc"
Check: Package existence for "gcc-c++"
Node Name     Available                 Required                  Status
orac2         gcc-c++-4.4.7-11.el6      gcc-c++-4.4.4             passed
orac1         gcc-c++-4.4.7-11.el6      gcc-c++-4.4.4             passed
Result: Package existence check passed for "gcc-c++"
Check: Package existence for "ksh"
Node Name     Available                 Required                  Status
orac2         ksh-20120801-21.el6.1     ksh-...                   passed
orac1         ksh-20120801-21.el6.1     ksh-...                   passed
Result: Package existence check passed for "ksh"
Check: Package existence for "make"
Node Name     Available                 Required                  Status
orac2         make-3.81-20.el6          make-3.81                 passed
orac1         make-3.81-20.el6          make-3.81                 passed
Result: Package existence check passed for "make"
Check: Package existence for "glibc(x86_64)"
Node Name     Available                 Required                  Status
orac2         glibc(x86_64)-2.12-1.149.el6 glibc(x86_64)-2.12        passed
orac1         glibc(x86_64)-2.12-1.149.el6 glibc(x86_64)-2.12        passed
Result: Package existence check passed for "glibc(x86_64)"
Check: Package existence for "glibc-devel(x86_64)"
Node Name     Available                 Required                  Status
orac2         glibc-devel(x86_64)-2.12-1.149.el6 glibc-devel(x86_64)-2.12 passed
orac1         glibc-devel(x86_64)-2.12-1.149.el6 glibc-devel(x86_64)-2.12 passed
Result: Package existence check passed for "glibc-devel(x86_64)"
Check: Package existence for "libaio(x86_64)"
Node Name     Available                 Required                  Status
orac2         libaio(x86_64)-0.3.107-10.el6 libaio(x86_64)-0.3.107    passed
orac1         libaio(x86_64)-0.3.107-10.el6 libaio(x86_64)-0.3.107    passed
Result: Package existence check passed for "libaio(x86_64)"
Check: Package existence for "libaio-devel(x86_64)"
Node Name     Available                 Required                  Status
orac2         libaio-devel(x86_64)-0.3.107-10.el6 libaio-devel(x86_64)-0.3.107 passed
orac1         libaio-devel(x86_64)-0.3.107-10.el6 libaio-devel(x86_64)-0.3.107 passed
Result: Package existence check passed for "libaio-devel(x86_64)"
Check: Package existence for "nfs-utils"
Node Name     Available                 Required                  Status
orac2         nfs-utils-1.2.3-26.el6    nfs-utils-1.2.3-15        passed
orac1         nfs-utils-1.2.3-26.el6    nfs-utils-1.2.3-15        passed
Result: Package existence check passed for "nfs-utils"
Checking availability of ports "6200,6100" required for component "Oracle Notification Service (ONS)"
Node Name         Port Number   Protocol      Available     Status
orac2             6200          TCP           yes           successful
orac1             6200          TCP           yes           successful
orac2             6100          TCP           yes           successful
orac1             6100          TCP           yes           successful
Result: Port availability check passed for ports "6200,6100"
Checking for multiple users with UID value 0
Result: Check for multiple users with UID value 0 passed
Check: Current group ID
Result: Current group ID check passed
Starting check for consistency of primary group of root user
Node Name                             Status
orac2                                 passed
orac1                                 passed
Check for consistency of root user's primary group passed
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
The NTP configuration file "/etc/ntp.conf" is available on all nodes
NTP Configuration file check passed
Checking daemon liveness...
Check: Liveness for "ntpd"
Node Name                             Running?
orac2                                 yes
orac1                                 yes
Result: Liveness check passed for "ntpd"
Check for NTP daemon or service alive passed on all nodes
Checking whether NTP daemon or service is using UDP port 123 on all nodes
Check for NTP daemon or service using UDP port 123
Node Name                             Port Open?
orac2                                 yes
orac1                                 yes
NTP common Time Server Check started...
NTP Time Server "193.27.209.1" is common to all nodes on which the NTP daemon is running
NTP Time Server "194.29.130.252" is common to all nodes on which the NTP daemon is running
Check of common NTP Time Server passed
Clock time offset check from NTP Time Server started...
Checking on nodes "[orac2, orac1]"...
Check: Clock time offset from NTP Time Server
Time Server: 193.27.209.1
Time Offset Limit: 1000.0 msecs
Node Name     Time Offset               Status
orac2         -355.25                   passed
orac1         -124.19                   passed
Time Server "193.27.209.1" has time offsets that are within permissible limits for nodes "[orac2, orac1]".
Time Server: 194.29.130.252
Time Offset Limit: 1000.0 msecs
Node Name     Time Offset               Status
orac2         -358.87                   passed
orac1         -109.63                   passed
Time Server "194.29.130.252" has time offsets that are within permissible limits for nodes "[orac2, orac1]".
Clock time offset check passed
Result: Clock synchronization check using Network Time Protocol(NTP) passed
Checking Core file name pattern consistency...
Core file name pattern consistency check passed.
Checking to make sure user "grid" is not in "root" group
Node Name     Status                    Comment
orac2         passed                    does not exist
orac1         passed                    does not exist
Result: User "grid" is not part of "root" group. Check passed
Check default user file creation mask
Node Name     Available                 Required                  Comment
orac2         0022                      0022                      passed
orac1         0022                      0022                      passed
Result: Default user file creation mask check passed
Checking integrity of file "/etc/resolv.conf" across nodes
Checking the file "/etc/resolv.conf" to make sure only one of domain and search entries is defined
WARNING:
PRVF-5640 : Both search and domain entries are present in file "/etc/resolv.conf" on the following nodes: orac1,orac2
Checking if domain entry in file "/etc/resolv.conf" is consistent across the nodes...
Checking file "/etc/resolv.conf" to make sure that only one domain entry is defined
More than one "domain" entry does not exist in any "/etc/resolv.conf" file
All nodes have same "domain" entry defined in file "/etc/resolv.conf"
Checking if search entry in file "/etc/resolv.conf" is consistent across the nodes...
Checking file "/etc/resolv.conf" to make sure that only one search entry is defined
More than one "search" entry does not exist in any "/etc/resolv.conf" file
All nodes have same "search" order defined in file "/etc/resolv.conf"
Checking DNS response time for an unreachable node
Node Name                             Status
orac1                                 passed
orac2                                 passed
The DNS response time for an unreachable node is within acceptable limit on all nodes
Check for integrity of file "/etc/resolv.conf" passed
Check: Time zone consistency
Result: Time zone consistency check passed
Checking integrity of name service switch configuration file "/etc/nsswitch.conf" ...
Checking if "hosts" entry in file "/etc/nsswitch.conf" is consistent across nodes...
Checking file "/etc/nsswitch.conf" to make sure that only one "hosts" entry is defined
More than one "hosts" entry does not exist in any "/etc/nsswitch.conf" file
All nodes have same "hosts" entry defined in file "/etc/nsswitch.conf"
Check for integrity of name service switch configuration file "/etc/nsswitch.conf" passed
Checking daemon "avahi-daemon" is not configured and running
Check: Daemon "avahi-daemon" not configured
Node Name     Configured                Status
orac2         yes                       failed
orac1         yes                       failed
Daemon not configured check failed for process "avahi-daemon"
Check: Daemon "avahi-daemon" not running
Node Name     Running?                  Status
orac2         yes                       failed
orac1         yes                      failed
Daemon not running check failed for process "avahi-daemon"

Yes, i can.
Node1.
[grid@orac1 grid]$ ping 10.154.137.101
PING 10.154.137.101 (10.154.137.101) 56(84) bytes of data.
64 bytes from 10.154.137.101: icmp_seq=1 ttl=64 time=0.105 ms
64 bytes from 10.154.137.101: icmp_seq=2 ttl=64 time=0.089 ms
64 bytes from 10.154.137.101: icmp_seq=3 ttl=64 time=0.056 ms
64 bytes from 10.154.137.101: icmp_seq=4 ttl=64 time=0.086 ms
^C
--- 10.154.137.101 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3098ms
rtt min/avg/max/mdev = 0.056/0.084/0.105/0.017 ms
[grid@orac1 grid]$ ping 10.154.137.102
PING 10.154.137.102 (10.154.137.102) 56(84) bytes of data.
64 bytes from 10.154.137.102: icmp_seq=1 ttl=64 time=2.15 ms
64 bytes from 10.154.137.102: icmp_seq=2 ttl=64 time=0.497 ms
64 bytes from 10.154.137.102: icmp_seq=3 ttl=64 time=0.364 ms
^C
--- 10.154.137.102 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2495ms
rtt min/avg/max/mdev = 0.364/1.003/2.150/0.813 ms
[grid@orac1 grid]$ ping 10.154.138.101
PING 10.154.138.101 (10.154.138.101) 56(84) bytes of data.
64 bytes from 10.154.138.101: icmp_seq=1 ttl=64 time=0.059 ms
64 bytes from 10.154.138.101: icmp_seq=2 ttl=64 time=0.173 ms
64 bytes from 10.154.138.101: icmp_seq=3 ttl=64 time=0.046 ms
64 bytes from 10.154.138.101: icmp_seq=4 ttl=64 time=0.056 ms
^C
--- 10.154.138.101 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3205ms
rtt min/avg/max/mdev = 0.046/0.083/0.173/0.052 ms
[grid@orac1 grid]$ ping 10.154.138.102
PING 10.154.138.102 (10.154.138.102) 56(84) bytes of data.
64 bytes from 10.154.138.102: icmp_seq=1 ttl=64 time=1.80 ms
64 bytes from 10.154.138.102: icmp_seq=2 ttl=64 time=0.418 ms
64 bytes from 10.154.138.102: icmp_seq=3 ttl=64 time=0.899 ms
^C
--- 10.154.138.102 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2860ms
rtt min/avg/max/mdev = 0.418/1.041/1.808/0.577 ms
[grid@orac1 grid]$
Node2.
[grid@orac2 ~]$ ping 10.154.137.101
PING 10.154.137.101 (10.154.137.101) 56(84) bytes of data.
64 bytes from 10.154.137.101: icmp_seq=1 ttl=64 time=0.537 ms
64 bytes from 10.154.137.101: icmp_seq=2 ttl=64 time=1.79 ms
64 bytes from 10.154.137.101: icmp_seq=3 ttl=64 time=0.733 ms
^C
--- 10.154.137.101 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2774ms
rtt min/avg/max/mdev = 0.537/1.021/1.794/0.552 ms
[grid@orac2 ~]$ ping 10.154.137.102
PING 10.154.137.102 (10.154.137.102) 56(84) bytes of data.
64 bytes from 10.154.137.102: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from 10.154.137.102: icmp_seq=2 ttl=64 time=0.106 ms
64 bytes from 10.154.137.102: icmp_seq=3 ttl=64 time=0.039 ms
64 bytes from 10.154.137.102: icmp_seq=4 ttl=64 time=0.039 ms
^C
--- 10.154.137.102 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3282ms
rtt min/avg/max/mdev = 0.039/0.056/0.106/0.029 ms
[grid@orac2 ~]$ ping 10.154.138.101
PING 10.154.138.101 (10.154.138.101) 56(84) bytes of data.
64 bytes from 10.154.138.101: icmp_seq=1 ttl=64 time=0.718 ms
64 bytes from 10.154.138.101: icmp_seq=2 ttl=64 time=0.515 ms
64 bytes from 10.154.138.101: icmp_seq=3 ttl=64 time=0.504 ms
^C
--- 10.154.138.101 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2468ms
rtt min/avg/max/mdev = 0.504/0.579/0.718/0.098 ms
[grid@orac2 ~]$ ping 10.154.138.102
PING 10.154.138.102 (10.154.138.102) 56(84) bytes of data.
64 bytes from 10.154.138.102: icmp_seq=1 ttl=64 time=0.058 ms
64 bytes from 10.154.138.102: icmp_seq=2 ttl=64 time=0.087 ms
64 bytes from 10.154.138.102: icmp_seq=3 ttl=64 time=0.052 ms
64 bytes from 10.154.138.102: icmp_seq=4 ttl=64 time=0.090 ms
^C
--- 10.154.138.102 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3755ms
rtt min/avg/max/mdev = 0.052/0.071/0.090/0.019 ms
[grid@orac2 ~]$

Multicast group 224.0.1.40 !

Similar Messages

Maybe you are looking for