BAM Cluster setup - issue with whole server migration configuration

Question

HI,
We are working on a SOA , BAM , BPM Cluster setup on OEL VMs
With Admin server running on Host1 and Soa_server1, BAM_server1 , Host2 - Soa_server2 , Bam_server2.
We were successfully able to setup clustering for Soa without using the webTier utilities in our environment, Just by adding entries in the /etc/hosts file.
Followed the document - except for web tier setup
http://www.namredlek.nl/orasoa/InstallSOASuite11gOnCluster_v1.pdf
1)     Installed Weblogic 11g.
2)     Soa 11g.
3)     Domain creation
4) Configured Node manager
5) Soa Clustering completed successfully.
6) Domain up and running with SOA_Cluster up and running.
7)     Extended the domain with BAM
The issue revolves when we are doing teh Migration configurations from the console for BAM and we restart BAM server we get an error -
Apr 14, 2011 2:30:35 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'bam_server1'
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
and Bam server goes to Failed Not Restartable state.

Answer 1

The error is clearly out there
java.io.IOException: Command '/oracle/Shared_MWHome/user_projects/domains/SOA_Domain/bin/server_migration/wlsifconfig.sh -addif eth0 192.168.1.6 255.255.255.0 ' returned an unsuccessful exit code '1'. Check NM logs for script output.
This error occurs due to a failure in adding the virtual IP of BAM server to the network interface you have specified in nodemanager.properties.
You need to check whether you have specified the correct interface and subnet mask in node manager.properties as below :
The fourth step is to edit the Node Manager's properties file. This file is called nodemanager.properties
and is located in the ORACLE_BASE/product/osbmw/wlserver_10.3/common/nodemanager directory.
For server migration to work properly, you need to add the properties listed below:
Interface=eth0
NetMask=255.255.255.0
UseMACBroadcast=true
· Interface
This property specifies the interface name for the floating IP (for example, eth0).
· NetMask
This property specifies the net mask for the interface for the floating IP. The net mask should the
same as the net mask on the interface; 255.255.255.0 is used as an example in this document.
· UseMACBroadcast
This property specifies whether or not to use a node's MAC address when sending ARP packets,
that is, whether or not to use the -b flag in the arping command.