![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| IP Networking Questions involving TCP/IP, Routers, Hubs, Network protocols, etc go here. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Clustering Solaris Zones/Containers | trouphaz | SUN Solaris | 8 | 04-21-2008 11:10 AM |
| Clustering or not | superlouis | UNIX for Dummies Questions & Answers | 0 | 09-06-2006 02:52 AM |
| Clustering solution for RH Linux AS and Solaris x86/AMD 64 | izy100 | UNIX for Advanced & Expert Users | 3 | 03-02-2005 09:01 PM |
| Disk Array & Clustering | champion | UNIX for Dummies Questions & Answers | 1 | 02-04-2003 05:43 AM |
| text boxes, radio buttons , check boxes in c++ on unix | devy8 | High Level Programming | 3 | 07-07-2001 02:58 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Can someone please help me to cluster two SUN Ultra 5 Boxes to run a application ? I am running Solaris 7 with two Ethernet NICs in each box. The Primary nics have a address of 10.10.10.24x and the other two nics have a multicast address of 224.0.1.27 each. I want to run a application at work (cannot be mentioned here) which requires that the machines be able to ping each other on either of the interfaces. I do not know how to configure routing differently for both the interfaces, such that the packets for network 10 go to hme0 and the multicast packets for network 224 go to hme1. Both the computers go out to the internet using 10.10.10.1 as their gateway. They are the only two machines on the network for multicast. Please help me as soon as possible so that I can get this thing over with and let me know if any other details of my configuration are required. I am very sorry for not being able to name the application that I am going to run after they get clustered. Please help as soon as possible
|
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
You use the <B> route </B> command to set up two static routes in each platform to instruct the kernel to route packets to IP address x.z.w.v via interface FOO and IP address x.z.w.vv via interface FOOBAR.
Similar idea for the other platform. After you get it right, you can add the route commands to the boot scripts to make this automatic on system boot. |
|
#3
|
|||
|
|||
|
Already done that
I've already added the route statement and it does show the route in the netstat -r command. But when I try to ping the subnet on the second interface, it gets lost. I did a traceroute and found that the packets are still being directed on the first interface. Looks like the first interface is default and so everything goes there. Don't know how to change that. The file /etc/defaultrouter is not present.
|
|
#4
|
||||
|
||||
|
Please to the output of both the <B> route -n </B> and <B> ifconfig </B> command on each platform and upload the results.
|
|
#5
|
|||
|
|||
|
Output of commands
Here are the outputs for the Machine:
IFCONFIG -A lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.10.10.240 netmask ffffff00 broadcast 10.10.10.255 ether 8:0:20:f2:78:22 hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 224.0.1.27 netmask f0000000 broadcast 239.255.255.255 ether 8:0:20:f2:78:22 NETSTAT -R Routing Table: Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 10.10.10.0 trafficserver U 3 2 hme0 224.0.0.0 trafficserver1 U 2 0 hme1 224.0.0.0 trafficserver U 3 0 hme0 localhost localhost UH 0 16 lo0 I am trying to ping 224.0.1.27 and the trace shows that it is going through the first interface (hme0) instead of hme1. |
|
#6
|
||||
|
||||
|
How about the other machine? Could you send the ifconfig and netstat -r info? (both machine a and b)
|
|
#7
|
|||
|
|||
|
Got it Done ......!!!!!!!
Hey Neo,
Thanx a bunch for the interest shown in the problem. I realize I did not provide enough info in the first post itself. I actually got it working now. I was making the mistake of assigning the IP address of the secondary interface as a 224.x.x.x IP. That was the problem. I gave it a valid 10.10.20.x IP and it liked it and then I gave the Multicast IP in the App that I was running, and they work just fine now. The lesson is, we cannot give a Multicast IP Address directly to a interface on a SUN Box. Please correct me if I am wrong here, but thats what I felt out of all this. Thanx a lot for ur help. Keyur Lavingia Network Engineer |
|||
| Google The UNIX and Linux Forums |
| Thread Tools | |
| Display Modes | |
|
|