- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Problems whith cluster ( interface standby)
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 02:01 AM
09-21-2006 02:01 AM
Problems whith cluster ( interface standby)
Please I need help.
when executed the cmcheckconf cmclconfig.ascii,
Show this:
Checking cluster file: cmclconfig.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ............... Done
Warning: The disk at /dev/dsk/c30t3d7 on node gfho3 does not have an ID, or a disk label.
Warning: Disks which do not have IDs cannot be included in the topology description.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c3t6d0 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t0d5 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t0d5 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t0d6 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t0d6 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t6d1 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t6d2 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t6d1 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t6d2 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t1d6 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t1d6 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t1d7 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t1d7 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t3d7 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c30t4d0 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t3d7 on node gfho3. Use pvcreate to give the disk an identifier.
Error: Unable to determine a unique identifier for physical volume /dev/dsk/c35t4d0 on node gfho3. Use pvcreate to give the disk an identifier.
Warning: Volume group /dev/vgsgfprd31 is configured differently on node gfho3 than on node gfprd3
Warning: Volume group /dev/vgsgfprd31 is configured differently on node gfprd3 than on node gfho3
Error: Volume group /dev/vgsgfprd31 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c30t3d7 on node gfprd3 (23899492451039792846).
Error: Volume group /dev/vgsgfprd31 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c35t4d0 on node gfprd3 (23899492451039792847).
Error: Volume group /dev/vgsgfprd31 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c35t3d7 on node gfprd3 (23899492451039792846).
Error: Volume group /dev/vgsgfprd31 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c30t4d0 on node gfprd3 (23899492451039792847).
Warning: Volume group /dev/vgsgfprd32 is configured differently on node gfho3 than on node gfprd3
Warning: Volume group /dev/vgsgfprd32 is configured differently on node gfprd3 than on node gfho3
Error: Volume group /dev/vgsgfprd32 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c30t0d5 on node gfprd3 (23899492451039792848).
Error: Volume group /dev/vgsgfprd32 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c35t0d5 on node gfprd3 (23899492451039792848).
Warning: Volume group /dev/vgsgfprd33 is configured differently on node gfho3 than on node gfprd3
Warning: Volume group /dev/vgsgfprd33 is configured differently on node gfprd3 than on node gfho3
Error: Volume group /dev/vgsgfprd33 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c35t0d6 on node gfprd3 (23899492451039792849).
Error: Volume group /dev/vgsgfprd33 on node gfho3 does not appear to have a physical volume corresponding to /dev/dsk/c30t0d6 on node gfprd3 (23899492451039792849).
Error: Interface lan15 on gfho3 has an IP address on it
(10.142.8.94), but the configuration file doesn't have it.
This may be caused by a local switch orchanges in the network configuration.
Error: Network interface lan11 cannot be found on node gfprd3
Error: gfprd3 lan11 can communicate with gfprd3 lan14 over subnet 0.0.0.0
on the IP level, but not on the DLPI level.
There is possibly a network component between the two interfaces
that does not allow any data link level traffic through, which violates
a ServiceGuard requirement.
Error: gfprd3 lan14 can communicate with gfprd3 lan11 over subnet 0.0.0.0
on the IP level, but not on the DLPI level.
There is possibly a network component between the two interfaces
that does not allow any data link level traffic through, which violates
a ServiceGuard requirement.
Warning: Network interface lan15 on node gfprd3 couldn't talk to itself.
Error: lan15 on node gfprd3 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any other lan.
Failed to evaluate network
cmcheckconf : Unable to reconcile configuration file cmclconfig.ascii
with discovered configuration information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 02:16 AM
09-21-2006 02:16 AM
Re: Problems whith cluster ( interface standby)
You appear to have a lot of LVM errors and Networkin gerrors that you need to fix first
check your LVM configuration and also your networkl topology, cabling, and configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 02:28 AM
09-21-2006 02:28 AM
Re: Problems whith cluster ( interface standby)
I will fix LVM. But the network is wrong, I can´t change for standby the interface lan15, how i do this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 04:18 AM
09-21-2006 04:18 AM
Re: Problems whith cluster ( interface standby)
For an interface to be a standby LAN, it must have pohysical connectivity to a configured LAN, which can be tested using linkloop.
E.g. if lan1 is configured, on both nodes, and lan3 is left unconfigured, but you can linkloop from lan1 on one node to th eother node's lan1 AND both lan3 ports, then this could be considered as a standby.
This gets tested at cmcheckconf and cmapplyconf runtime, and if any issues are found then you are either unable to use the lan. or you could get a number of different messages. Your error is that lan15 is unable to talk to itself and it cannot link to any other lans. Also note:
Error: Interface lan15 on gfho3 has an IP address on it
(10.142.8.94), but the configuration file doesn't have it.
This may be caused by a local switch orchanges in the network configuration.
Error: Network interface lan11 cannot be found on node gfprd3
Error: gfprd3 lan11 can communicate with gfprd3 lan14 over subnet 0.0.0.0
on the IP level, but not on the DLPI level.
There is possibly a network component between the two interfaces
that does not allow any data link level traffic through, which violates
a ServiceGuard requirement.
Error: gfprd3 lan14 can communicate with gfprd3 lan11 over subnet 0.0.0.0
on the IP level, but not on the DLPI level.
There is possibly a network component between the two interfaces
that does not allow any data link level traffic through, which violates
a ServiceGuard requirement.
You need to fix these errors in your network first
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 05:47 AM
09-21-2006 05:47 AM
Re: Problems whith cluster ( interface standby)
My friend, I have more one problem,
Have done upgrade of the my server.
But the path devides has change done.
I would like to see VG belongs the disk.
how do this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 05:53 AM
09-21-2006 05:53 AM
Re: Problems whith cluster ( interface standby)
or
If you worried about cluster lock device file got changed and don't want to compile then you have to create and edit ioconfig file to reflect Controller numbers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:01 AM
09-22-2006 01:01 AM
Re: Problems whith cluster ( interface standby)
but I have other problem:
Sep 22 09:44:46 fg33 CM-CMD[10821]: cmrunpkg -n fg33 OVPI-HO
Sep 22 09:44:46 fg33 cmcld: Request from node fgd33 to start package OVPI-HO on node fg33.
Sep 22 09:44:46 fg33 cmcld: Executing '/etc/cmcluster/OVPI-HO/OVPI-HO.cntl start' for package OVPI-HO, as service PKG*62722.
Sep 22 09:44:46 fg33 cmcld: Service PKG*62722 terminated due to an exit(1).
Sep 22 09:44:46 fg33 cmcld: Package OVPI-HO run script exited with NO_RESTART.
Sep 22 09:44:46 fg33 cmcld: Examine the file /etc/cmcluster/OVPI-HO/OVPI-HO.cntl.log for more details.
Sep 22 09:44:46 fg33 cmcld: Switching disabled on package OVPI-HO.
########### Node "fg33": Starting package at Fri Sep 22 09:47:18 SAT 2006 ###########
Sep 22 09:47:18 - "fg33": Activating volume group /dev/vgsgfhml31 with exclusive option.
vgchange: Volume group "/dev/vgsgfhml31" does not exist in the "/etc/lvmtab" file.
ERROR: Function activate_volume_group
ERROR: Failed to activate /dev/vgsgfhml31
Sep 22 09:47:18 - Node "fg33": Deactivating volume group /dev/vgsgfhml31
vgchange: Volume group "/dev/vgsgfhml31" does not exist in the "/etc/lvmtab" file.
ERROR: Function deactivate_volume_group
ERROR: Failed to deactivate /dev/vgsgfhml31
Sep 22 09:47:18 - Node "fg33": Deactivating volume group /dev/vgsgfhml32
vgchange: Volume group "/dev/vgsgfhml32" does not exist in the "/etc/lvmtab" file.
ERROR: Function deactivate_volume_group
ERROR: Failed to deactivate /dev/vgsgfhml32
Sep 22 09:47:18 - Node "fg33": Deactivating volume group /dev/vgsgfhml33
vgchange: Volume group "/dev/vgsgfhml33" does not exist in the "/etc/lvmtab" file.
ERROR: Function deactivate_volume_group
ERROR: Failed to deactivate /dev/vgsgfhml33
########### Node "fg33": Package start failed at Fri Sep 22 09:47:18 SAT 2006 ###########
In lvmtab:
strings /etc/lvmtab
/dev/vg00
/dev/dsk/c0t6d0
/dev/dsk/c8t6d0
/dev/vgsgfprd32
/dev/dsk/c12t0d5
/dev/vgsgfprd33
/dev/dsk/c12t0d6
/dev/vgsgfhm132
/dev/dsk/c12t1d6
/dev/vgsgfhm133
/dev/dsk/c12t1d7
/dev/vgsgfprd31
/dev/dsk/c12t3d7
/dev/dsk/c12t4d0
/dev/vgsgfhm131
/dev/dsk/c12t6d1
/dev/dsk/c12t6d2
I do vgchange -a y vgsgfhm131, it´s OK.
But when active the pkg don´t work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:05 AM
09-22-2006 01:05 AM
Re: Problems whith cluster ( interface standby)
You need to deactivate them first and then issue
vgchange -a n /dev/vgXX
vgchange -s y /dev/vgXX
then restart package.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:16 AM
09-22-2006 01:16 AM
Re: Problems whith cluster ( interface standby)
Usage: vgchange
{-a Availability -q Quorum [-l] [-p] [-s] [VolumeGroupName... ]}
{[-S shareable] -c cluster VolumeGroupName}
{[-P parallel_nomwc_resync_count]}
There are error of sintax
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:20 AM
09-22-2006 01:20 AM
Re: Problems whith cluster ( interface standby)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:25 AM
09-22-2006 01:25 AM
Re: Problems whith cluster ( interface standby)
vgchange -a n vgsgfhm131
vgchange -c y vgsgfhm131
when start the pkg:
cmrunpkg -n node pkg
Did pkg have that start,OK?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 01:35 AM
09-22-2006 01:35 AM
Re: Problems whith cluster ( interface standby)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 05:07 AM
09-22-2006 05:07 AM
Re: Problems whith cluster ( interface standby)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2006 05:07 AM
09-22-2006 05:07 AM