- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cmquerycl not work
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
08-25-2008 01:32 AM
08-25-2008 01:32 AM
cmquerycl not work
when i do this command :
# cmquerycl -v -C /etc/cmcluster/conf.ascii -n cancer -n taurus
Warning: Unable to determine local domain name for cancer1
Looking for other clusters ... Done
Gathering storage information
Found 10 devices on node cancer
Found 14 devices on node taurus
Analysis of 24 devices should take approximately 3 seconds
0%----10%----20%--Error reading device /dev/dsk/c4t0d0 0x8
--30%----40%----50%----60%----70%----80%----90%----100%
Found 3 volume groups on node cancer
Found 3 volume groups on node taurus
Analysis of 6 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Note: Disks were discovered which are not in use by either LVM or VxVM.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
Gathering network information
Beginning network probing
Completed network probing
taurus lan0 can communicate with taurus lan2 over subnet 192.168.1.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.
taurus lan2 can communicate with taurus lan0 over subnet 192.168.1.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.
Failed to evaluate network
Failed to gather configuration information.
there any step i miss? plz help
thx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 02:26 AM
08-25-2008 02:26 AM
Re: cmquerycl not work
Check
1>/etc/cmcluster/cmclnodelist
2> /etc/hosts
3> also check subnet for heartbat ip it should be on the same subnet
4>All nodes should be in the same subnet
Regards
Atul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 02:42 AM
08-25-2008 02:42 AM
Re: cmquerycl not work
/etc/hosts entries
e.g
IP hostname FQDN
....
...
...
/etc/cmcluster/cmclnodelist
hostname root
hostname root
And most important...
How are you connecting these two nodes here...
Hearbeat packets travels at data link level ..
So make sure network connectivity is as per SG guidelines
Better you provide your network details related to this setup...
Regds...DK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 05:20 AM
08-25-2008 05:20 AM
Re: cmquerycl not work
It is kind of nslookup error. Make sure all the above said files are with the correct hostnames.
># cmquerycl -v -C /etc/cmcluster/conf.ascii -n cancer -n taurus
>Warning: Unable to determine local domain name for cancer1
It says cancer1 (one)
cancer and cancer1 - make sure which one is your correct hostname
Rgds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 09:01 AM
08-25-2008 09:01 AM
Re: cmquerycl not work
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 have a network component in place that prevents Low Level Network traffic (DLPI) but allows tcp/ip traffic.
Perhaps a router? or a switch that has some settings configured to prevent DLPI?
This has nothing to do with hosts, DNS etc as it CAN connect using IP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 11:47 PM
08-25-2008 11:47 PM
Re: cmquerycl not work
i doesn't get the DLPI, i ask to network admin they also doesn't know bout DLPI.
i only use 1 switch n use 1 lan card each other.
and how bout this
Note: Disks were discovered which are not in use by either LVM or VxVM.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
what must i do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2008 12:06 AM
08-26-2008 12:06 AM
Re: cmquerycl not work
if you want to make the disk as a part of cluster u can make it. Is there was any provison u did for that particular disk .
Regards
Atul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2008 12:22 AM
08-26-2008 12:22 AM