I take it that 'node1' is your svc label?
Try using a subnet for this different than the boot adapters are
using...this should cause the network to be created as 'aliased'.
There was work done in HACMP 5.1 to make alias'd networks the default,
these use a different subnet for the svc label. There were some
special things one had to do in configuration (I can't remember
exactly what they were...) to configure a traditional network. Anyway,
but the svc label on a different subnet and try to sync/verify...the
other thing you can do is look at your network definition...smitty
hacmp ->> down to change/show network and see if the network is marked
as aliased. IF it is, then this svc label on the same subnet as the
boot is definitely a problem....
bigtiny
empete2000@yahoo.com (Pete's) wrote in message news:<6724a51f.0410060530.4f137339@posting.google. com>...
> bigtiny@mac.com (bigtiny) wrote in message news:<c4435822.0410040837.677a83e1@posting.google. com>...
> > Can you post your cluster configuration?
> > You've added the node2 and its ethernet adapters to your configuration, right?
> >
> > bigtiny
> >
> > empete2000@yahoo.com (Pete's) wrote in message news:<6724a51f.0410011308.61552126@posting.google. com>...
> > > bigtiny@mac.com (bigtiny) wrote in message news:<c4435822.0410010536.528c4778@posting.google. com>...
> > > > You say that clcomd is running on node2...have you verified this via
> > > > lssrc ?
> > > > There is a known AIX problem that sometimes causes clcomd NOT to start
> > > > automatically. If this happens, you'll see this kind of error. The
> > > > other errors may be side effects of this problem...I wouldnt' worry
> > > > about trying to solve them until you solve this initial problem. Also,
> > > > did you reboot node2 after installing HACMP? If not, then do so
> > > > before trying to start cluster services.
> > > >
> > > > bigtiny
> > > Snipped some text.
> > >
> > > I verified it once more, it is showing as active. After installing
> > > HA, OS maintenance levels and patches, the server was rebooted.
> > >
> > > TIA
> > > Pete's
>
> Cluster configuration is below. I have added the ethernet adapters to the config.
>
> TIA,
> Pete's
>
>
> Cluster Topology:
>
> NODE node1:
> Network net_ether_01
> node1 192.168.3.31
> node1_boot 192.168.3.30
> node1_stby 192.168.14.38
> Network net_rs232_01
> node1_tty1 /dev/tty1
>
> NODE node2:
> Network net_ether_01
> node2_boot 192.168.3.45
> node2_stby 192.168.14.5
> Network net_rs232_01
> node2_tty1 /dev/tty1
>
>
> Resource Group:
>
> Resource Group Name RG_1
> Node Relationship cascading
> Site Relationship ignore
> Participating Node Name(s) node1 node2
> Dynamic Node Priority
> Service IP Label node1
> Filesystems ALL
> Filesystems Consistency Check logredo
> Filesystems Recovery Method parallel
> Filesystems/Directories to be exported
> Filesystems to be NFS mounted
> Network For NFS Mount
> Volume Groups vg01
> Concurrent Volume Groups
> Use forced varyon for volume groups, if necessary false
> Disks
> GMD Replicated Resources
> PPRC Replicated Resources
> Connections Services
> Fast Connect Services
> Shared Tape Resources
> Application Servers APP_Server_1 APP_Server_2
> Highly Available Communication Links
> Primary Workload Manager Class
> Secondary Workload Manager Class
> Delayed Fallback Timer
> Miscellaneous Data Resource Group Attributes
> Automatically Import Volume Groups false
> Inactive Takeover true
> Cascading Without Fallback false
> SSA Disk Fencing false
> Filesystems mounted before IP configured false
> Run Time Parameters:
>
> Node Name node1
> Debug Level high
> Format for hacmp.out Standard
>
> Node Name node2
> Debug Level high
> Format for hacmp.out Standard