Logical Hostname fail to create

Hi,
I have installed Sun Cluster 3.2 on Solaris 10 10/08 with Kernel patch 138888-01
The cluster is a test cluster running on one node.
I have create 2 Local Zones with Exclusive IP
1. clrg create -n HOST:zone1,HOST:zone2 test-rg
2. I have add test-ip in /etc/hosts on the 2 zones
3. when I am trying to run the clrslh command to create the logical hostname I get the following errors
( I am using the GUI for the creation of the logical hostname)
clrslh (C189917) VALIDATE on resource OP-rs resource group test-rg exited with non-zero exit status
clrslh (C720144) validation on resource IP-rs in resource group test-rg on node HOST;ZONE failed
clrslh (C891200) Failed to create resource IP-rs
Can any one help to resolve this problem?
Thanks
Yacov

Hi
I have some information regarding this problem.
The /var/adm/messages* content regarding the problem
May 28 09:26:23 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hafoip_validate> for resource <test-ip>, resource group <test-rg>, node <za-dr-it-sp1:uat-mozambique2>, timeout <300> seconds
May 28 09:26:23 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 896918 daemon.notice] 10 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hafoip/hafoip_validate>:tag=<uat-mozambique2.test-rg.test-ip.2>: Calling security_clnt_connect(..., host=<za-dr-it-sp1>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
May 28 09:26:24 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 699104 daemon.error] VALIDATE failed on resource <test-ip>, resource group <test-rg>, time used: 0% of timeout <300, seconds>
When creating the logical hostname*
Command executed: /usr/cluster/bin/clreslogicalhostname create -g test-rg -p Resource_project_name= -p Failover_mode=NONE -p R_description=Failover\ network\ resource\ for\ SUNW.LogicalHostname:3 -h test-ip test-ip
Error message:
clreslogicalhostname: (C189917) VALIDATE on resource test-ip, resource group test-rg, exited with non-zero exit status.
clreslogicalhostname: (C720144) Validation of resource test-ip in resource group test-rg on node za-dr-it-sp1:uat-mozambique2 failed.
clreslogicalhostname: (C891200) Failed to create resource "test-ip".

Similar Messages

Creating Logical Hostname Resource - Resource contains invalid hostnames

I am desperately trying to create a shared ip address that my two-node zone cluster will utilize for a failover application. I have added the hostname/ip address pair to /etc/hosts and /etc/inet/ipnodes on both global nodes as well as within each zone cluster node. I then attempt to run the following:
# clrslh create -Z test -g test-rg -h foo.bar.com test-hostname-rs
which yields the following:
clrslh: host1.example.com:test - The hostname foo.bar.com is not authorized to be used in this zone cluster test.
clrslh: host1.example.com:test - Resource contains invalid hostnames.
clrslh: (C189917) VALIDATE on resource test-hostname-rs, resource group test-rg, exited with non-zero exit status.
clrslh: (C720144) Validation of resource test-hostname-rs in resource group test-rg on node host1 failed.
clrslh: (C891200) Failed to create resource "test:test-hostname-rs".
I have searched high and low. The only thing I found was the following:
http://docs.sun.com/app/docs/doc/820-4681/m6069?a=view
Which states: User the clzonecluster(1M) command to configure the hostnames to be used for this zone cluster and then rerun this command to create the resource.
I do not understand what it is saying. My guess is that I need to apply a hostname to the zone cluster. Granted, I don't know how to accomplish this. Halp?

The procedure to authorize the hostnames for the zone cluster is below:
clzc configure <zonecluster> (this will bring you under the zone cluster scope like below)
clzc:<zonecluster> add net
clzc:<zonecluster>:net> set address=<hostname>
clzc:<zonecluster>:net> end
clzc:<zonecluster> commit
clzc:<zonecluster>info (to verify the hostname)
After this operation, run the clrslh command to create the logical host resource
and the command should pass.
Thanks,
Prasanna Kunisetty

Failed to create RAID logical drive WAE-7371-k9

hi all we have cisco wae-7371-k9 , we wanna recreate RAID device using cd recovery. we booting on cd, and when we done with option numbers 2,3,5 succes but when we came on option 7, we cannot recreate RAID, it failed, following the log: Installer Main Menu: 1. Configure Network 2. Manufacture flash (done) 3. Install flash cookie 4. Install flash image from network 5. Install flash image from cdrom 6. Install flash image from disk 7. Recreate RAID device (WAE-674/7341/7371 only) 8. Wipe out disks and install .bin image 9. Exit (Eject and reboot) Choice [0]: 7 Recreate RAID device option is selected All disk data will be lost. Are you sure you want to recreate RAID array? [n]: y Saving random seed... dd: opening `/state/random-seed': No such file or directory No volume groups found Controllers found: 1 All data in logical drive 1 will be lost. Deleting: logical drive 1 ("") Command completed successfully. Controllers found: 1 A selected physical drive is not available for use. Command aborted. Failed to create RAID Logical drive. (1,2) MODEL: OE7371 FLASH: found, directory validated COOKIE: valid IMAGE: 4.3.5.7 FLASHDEV: /dev/sda what's wrong with wae ?if we run command show disk detail, all hard disk detected NO-HOSTNAME# sh disk det RAID Physical disk information: disk00: Ready JTX1470L 286102 MB disk01: Ready JTX1B24L 286102 MB disk02: Ready JTX1B9SL 286102 MB disk04: Ready JTWSEBWL 286102 MB disk05: Ready JTX0VYRL 286102 MB RAID Logical drive information: Mounted file systems: MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE% Disk encryption feature is disabled. can you help, what's the problem .?

Budi,
Please turn off the unit, make sure you reseat the disks and then try the CD-recovery in the following way:
2,3, 5,8,7,8, remove the disk and 9
Please log the session then we can see how it went
Hope this helps!
Jorge

Creating Logical hostname in sun cluster

Can someone tell me, what exactly logical hostname in sun cluster mean?
For registering logical hostname resource in failoover group, what exactly i need to specify
for example, i have two nodes in sun cluster , How to create or configure a logical hostanme and it should point to which IP Address ( Whether it should point to IP addresses of nodes in sun cluster). Can i get clarification on this?

Thanks Thorsten for ur continue help...
The output of clrs status abc_lg
=== Cluster Resources ===
Resource Name Node Name State Status Message
abc_lg node1 Offline Offline
node2 Offline Offline
The status is offline...
the output of clresourcegroup status
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
abc_rg node1 No Unmanaged
node2 No Unmanaged
You say that the resource should de enabled after creating the resource.. I am using GDS and i am just following the steps he provided to acheive high availabilty (in developers guide...)
I have 1) Logical hostname resorce.
2) Application resource in my failover resource group
When i bring online the failover resource group , what should my failover resource group status and the status of resource in my resource group

Problem in creating logical hostname resource

Hi all,
I have a cluster configured on 10.112.10.206 and 10.112.10.208
i have a resource group testrg
I want to create a logical hostname resource testhost
I have given a ip 10.112.10.245 in /etc/hosts file for testhost
I am creating a logical hostname resource by below command -
clrslh create -g testrg testhost
I am doing this on 206
As I do, the other node 208 becomes unreachable....I m not able to ping 208 but ssh is done from 206 to 208.
I am also not able to ping 10.112.10.245
Please help.

So, the physical IP addresses of your two nodes are:
10.112.10.206 node1
10.112.10.208 node2
And your logical host is:
10.112.10.245 testhost
Have you got a netmask set for this network? Is it 255.255.255.0 and is it set in /etc/netmasks?
It's most likely that this is the cause of the problem if you have different netmasks on the interfaces.
Tim
---

SC 3.2 - logical hostname create rpoblem

Hello
I am running with Sun Cluster 3.2 in two node cluster with IPMP. And we are using IBM Storage and metaset (Solaris Volume Manager) in the cluster.
While trying to create Sun Cluster resource logical hostname, I get this error. I was able to successfully create the data resource but the logical hostname resource is giving this error.
Command executed: /usr/cluster/bin/clreslogicalhostname create -g test-rg -p Resource_project_name=default -p R_description=Failover\ network\ resource\ for\ SUNW.LogicalHostname:3 -N group1@1:node1,group1@2:node22 -h test-rs test-rs
Error message:
clreslogicalhostname: <test-rs> cannot be mapped to an IP address
Please advise.

Hi,
The value you specified with -h option is the logical hostname that should be mapped to an IP address and is not
the resource name. The address mapping is possible if you have an entry for this hostname either in the /etc/hosts file or an entry in the name service
that you are using. Make sure that you have an entry in the /etc/hosts file for "test-rs" and retry the create operation.
BTW, You need not specify the -h option if your hostname
is same as the resource name, and resource name is resolvable.
From man page of clrslh command:
-h lhost[,]
--logicalhost lhost[,]
Specifies the list of logical hostnames that this resource represents. You must use the -h option either when more than one logical hostname is to be associated with the new logical hostname resource or when the logical hostname does not have the same name as the resource itself. All logical hostnames in the list must be on the same subnet. If you do not specify the -h option, the resource represents a single logical hostname whose name is the name of the resource itself.
You can use -h instead of setting the HostnameList property with -p. However, you cannot use -h and explicitly set HostnameList in the same command.
Thanks,
Prasanna Kunisetty

Including Logical Hostname as a Resource Dependency

Hi Folks,
We're setting up a Calendar Server. we assign a Logical Hostname resource on which the Calendar Clients connect to.
These are the steps that are used:
I created a Fail Over Resource Group called MS_RG_BUDDY and bring it online
scrgadm -a -g MS_RG_BUDDY -h mars,venus
I created a Logical Hostname resource EVERGREEN for this Fail Over resource group
scrgadm -a -L -g MS_RG_BUDDY -l EVERGREEN
scrgadm -c -j EVERGREEN -y R_description="LogicalHostname resource for evergreen"
Bring the Resource Group Online
scswitch -Z -g MS_RG_BUDDY
I create a HAStoragePlus Resources called disk-evergreen with two cluster file systems ( /var/opt/xyz and /var/opt/abc )
scrgadm -a -j disk-evergreen -g MS_RG_BUDDY -t SUNW.HAStoragePlus -x FileSystemMountPoints="/var/opt/xyz,/var/opt/abc" -x AffinityOn=TRUE
Enable the HAStoragePlus resource
scswitch -e -j disk-evergreen
Create a resource with a dependency on the HAStoragePlus resource
scrgadm -a -j core-rs -t SUNW.iws -g MS_RG_BUDDY -x IWS_serverroot=/opt/SUNWiws -y Resource_dependencies=disk-evergreen
I have a question. In the above command, we created a Resource_Dependency on the HAstoragePlus resource, should we also create dependency on the Logical hostname i.e should the Resource_dependency look like
Resource_dependencies=evergreen,disk-evergreen
Is this correct ?. Should we bother. Are there any other factors we might want to consder

Hartmut,
Thanks for your response, I think i wil use the explicit dependency :) since all our clients connect to the custer via this LogicalHostname.
Are you referring to this property ?
(CAL-RED-RG) Res Group network dependencies: True
Gotten from running the following command:
# ./scrgadm -pvv -g CAL-RED-RG
Res Group name: CAL-RED-RG
(CAL-RED-RG) Res Group RG_description: <NULL>
(CAL-RED-RG) Res Group mode: Failover
(CAL-RED-RG) Res Group management state: Managed
(CAL-RED-RG) Res Group RG_project_name: default
(CAL-RED-RG) Res Group RG_SLM_type: manual
(CAL-RED-RG) Res Group RG_affinities: <NULL>
(CAL-RED-RG) Res Group Auto_start_on_new_cluster: True
(CAL-RED-RG) Res Group Failback: False
(CAL-RED-RG) Res Group Nodelist: shaw telstra
(CAL-RED-RG) Res Group Maximum_primaries: 1
(CAL-RED-RG) Res Group Desired_primaries: 1
(CAL-RED-RG) Res Group RG_dependencies: <NULL>
(CAL-RED-RG) Res Group network dependencies: True
(CAL-RED-RG) Res Group Global_resources_used: <All>
(CAL-RED-RG) Res Group Pingpong_interval: 3600
(CAL-RED-RG) Res Group Pathprefix: <NULL>
(CAL-RED-RG) Res Group system: False
(CAL-RED-RG) Res Group Suspend_automatic_recovery: False
(CAL-RED-RG) Res name: redmeadows
(CAL-RED-RG:redmeadows) Res R_description: LogicalHostname resource for
redmeadows
(CAL-RED-RG:redmeadows) Res resource type: SUNW.LogicalHostname:2
(CAL-RED-RG:redmeadows) Res type version: 2
(CAL-RED-RG:redmeadows) Res resource group name: CAL-RED-RG
(CAL-RED-RG:redmeadows) Res resource project name: default
(CAL-RED-RG:redmeadows{shaw}) Res enabled: True
(CAL-RED-RG:redmeadows{telstra}) Res enabled: True
(CAL-RED-RG:redmeadows{shaw}) Res monitor enabled: True
(CAL-RED-RG:redmeadows{telstra}) Res monitor enabled: True
(CAL-RED-RG:redmeadows) Res strong dependencies: <NULL>
(CAL-RED-RG:redmeadows) Res weak dependencies: <NULL>
(CAL-RED-RG:redmeadows) Res restart dependencies: <NULL>
(CAL-RED-RG:redmeadows) Res offline restart dependencies: <NULL>
(CAL-RED-RG:redmeadows) Res property name: Retry_interval
(CAL-RED-RG:redmeadows:Retry_interval) Res property class: standard
(CAL-RED-RG:redmeadows:Retry_interval) Res property description: Time in w
hich monitor attempts to restart a failed resource Retry_count times.
(CAL-RED-RG:redmeadows:Retry_interval) Res property type: int
(CAL-RED-RG:redmeadows:Retry_interval) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: Retry_count
(CAL-RED-RG:redmeadows:Retry_count) Res property class: standard
(CAL-RED-RG:redmeadows:Retry_count) Res property description: Indicates th
e number of times a monitor restarts the resource if it fails.
(CAL-RED-RG:redmeadows:Retry_count) Res property type: int
(CAL-RED-RG:redmeadows:Retry_count) Res property value: 2
(CAL-RED-RG:redmeadows) Res property name: Thorough_probe_interval
(CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property class: standa
rd
(CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property description:
Time between invocations of a high-overhead fault probe of the resource.
(CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property type: int
(CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property value: 60
(CAL-RED-RG:redmeadows) Res property name: Cheap_probe_interval
(CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property class: standard
(CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property description: Tim
e between invocations of a quick fault probe of the resource.
(CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property type: int
(CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property value: 60
(CAL-RED-RG:redmeadows) Res property name: Failover_mode
(CAL-RED-RG:redmeadows:Failover_mode) Res property class: standard
(CAL-RED-RG:redmeadows:Failover_mode) Res property description: Modifies r
ecovery actions taken when the resource fails.
(CAL-RED-RG:redmeadows:Failover_mode) Res property type: enum
(CAL-RED-RG:redmeadows:Failover_mode) Res property value: HARD
(CAL-RED-RG:redmeadows) Res property name: PRENET_START_TIMEOUT
(CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property description: Max
imum execution time allowed for Prenet_Start method.
(CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: MONITOR_CHECK_TIMEOUT
(CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property description: Ma
ximum execution time allowed for Monitor_Check method.
(CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: MONITOR_STOP_TIMEOUT
(CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property description: Max
imum execution time allowed for Monitor_Stop method.
(CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: MONITOR_START_TIMEOUT
(CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property description: Ma
ximum execution time allowed for Monitor_Start method.
(CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: UPDATE_TIMEOUT
(CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property description: Maximum e
xecution time allowed for Update method.
(CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: VALIDATE_TIMEOUT
(CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property description: Maximum
execution time allowed for Validate method.
(CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: STOP_TIMEOUT
(CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property description: Maximum exe
cution time allowed for Stop method.
(CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property value: 300
(CAL-RED-RG:redmeadows) Res property name: START_TIMEOUT
(CAL-RED-RG:redmeadows:START_TIMEOUT) Res property class: standard
(CAL-RED-RG:redmeadows:START_TIMEOUT) Res property description: Maximum ex
ecution time allowed for Start method.
(CAL-RED-RG:redmeadows:START_TIMEOUT) Res property type: int
(CAL-RED-RG:redmeadows:START_TIMEOUT) Res property value: 500
(CAL-RED-RG:redmeadows) Res property name: CheckNameService
(CAL-RED-RG:redmeadows:CheckNameService) Res property class: extension
(CAL-RED-RG:redmeadows:CheckNameService) Res property description: Name se
rvice check flag
(CAL-RED-RG:redmeadows:CheckNameService) Res property pernode: False
(CAL-RED-RG:redmeadows:CheckNameService) Res property type: boolean
(CAL-RED-RG:redmeadows:CheckNameService) Res property value: TRUE
(CAL-RED-RG:redmeadows) Res property name: NetIfList
(CAL-RED-RG:redmeadows:NetIfList) Res property class: extension
(CAL-RED-RG:redmeadows:NetIfList) Res property description: List of IPMP g
roups on each node
(CAL-RED-RG:redmeadows:NetIfList) Res property pernode: False
(CAL-RED-RG:redmeadows:NetIfList) Res property type: stringarray
(CAL-RED-RG:redmeadows:NetIfList) Res property value: sc_ipmp0@1 sc_ipmp0@
2
(CAL-RED-RG:redmeadows) Res property name: HostnameList
(CAL-RED-RG:redmeadows:HostnameList) Res property class: extension
(CAL-RED-RG:redmeadows:HostnameList) Res property description: List of hos
tnames this resource manages
(CAL-RED-RG:redmeadows:HostnameList) Res property pernode: False
(CAL-RED-RG:redmeadows:HostnameList) Res property type: stringarray
(CAL-RED-RG:redmeadows:HostnameList) Res property value: redmeadows
(CAL-RED-RG) Res name: disk-red-rs
(CAL-RED-RG:disk-red-rs) Res R_description: Failover data service resourc
e for SUNW.HAStoragePlus:4
(CAL-RED-RG:disk-red-rs) Res resource type: SUNW.HAStoragePlus:4
(CAL-RED-RG:disk-red-rs) Res type version: 4
(CAL-RED-RG:disk-red-rs) Res resource group name: CAL-RED-RG
(CAL-RED-RG:disk-red-rs) Res resource project name: default
(CAL-RED-RG:disk-red-rs{shaw}) Res enabled: True
(CAL-RED-RG:disk-red-rs{telstra}) Res enabled: True
(CAL-RED-RG:disk-red-rs{shaw}) Res monitor enabled: True
(CAL-RED-RG:disk-red-rs{telstra}) Res monitor enabled: True
(CAL-RED-RG:disk-red-rs) Res strong dependencies: <NULL>
(CAL-RED-RG:disk-red-rs) Res weak dependencies: <NULL>
(CAL-RED-RG:disk-red-rs) Res restart dependencies: <NULL>
(CAL-RED-RG:disk-red-rs) Res offline restart dependencies: <NULL>
(CAL-RED-RG:disk-red-rs) Res property name: Retry_interval
(CAL-RED-RG:disk-red-rs:Retry_interval) Res property class: standard
(CAL-RED-RG:disk-red-rs:Retry_interval) Res property description: Time in
which monitor attempts to restart a failed resource Retry_count times.
(CAL-RED-RG:disk-red-rs:Retry_interval) Res property type: int
(CAL-RED-RG:disk-red-rs:Retry_interval) Res property value: 300
(CAL-RED-RG:disk-red-rs) Res property name: Retry_count
(CAL-RED-RG:disk-red-rs:Retry_count) Res property class: standard
(CAL-RED-RG:disk-red-rs:Retry_count) Res property description: Indicates t
he number of times a monitor restarts the resource if it fails.
(CAL-RED-RG:disk-red-rs:Retry_count) Res property type: int
(CAL-RED-RG:disk-red-rs:Retry_count) Res property value: 2
(CAL-RED-RG:disk-red-rs) Res property name: Failover_mode
(CAL-RED-RG:disk-red-rs:Failover_mode) Res property class: standard
(CAL-RED-RG:disk-red-rs:Failover_mode) Res property description: Modifies
recovery actions taken when the resource fails.
(CAL-RED-RG:disk-red-rs:Failover_mode) Res property type: enum
(CAL-RED-RG:disk-red-rs:Failover_mode) Res property value: SOFT
(CAL-RED-RG:disk-red-rs) Res property name: POSTNET_STOP_TIMEOUT
(CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property description: Ma
ximum execution time allowed for Postnet_stop method.
(CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: PRENET_START_TIMEOUT
(CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property description: Ma
ximum execution time allowed for Prenet_Start method.
(CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: MONITOR_CHECK_TIMEOUT
(CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property class: standar
d
(CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property description: M
aximum execution time allowed for Monitor_Check method.
(CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property value: 90
(CAL-RED-RG:disk-red-rs) Res property name: MONITOR_STOP_TIMEOUT
(CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property description: Ma
ximum execution time allowed for Monitor_Stop method.
(CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property value: 90
(CAL-RED-RG:disk-red-rs) Res property name: MONITOR_START_TIMEOUT
(CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property class: standar
d
(CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property description: M
aximum execution time allowed for Monitor_Start method.
(CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property value: 90
(CAL-RED-RG:disk-red-rs) Res property name: INIT_TIMEOUT
(CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property description: Maximum ex
ecution time allowed for Init method.
(CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: UPDATE_TIMEOUT
(CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property description: Maximum
execution time allowed for Update method.
(CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: VALIDATE_TIMEOUT
(CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property description: Maximu
m execution time allowed for Validate method.
(CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: STOP_TIMEOUT
(CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property description: Maximum ex
ecution time allowed for Stop method.
(CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property value: 1800
(CAL-RED-RG:disk-red-rs) Res property name: START_TIMEOUT
(CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property class: standard
(CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property description: Maximum e
xecution time allowed for Start method.
(CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property type: int
(CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property value: 90
(CAL-RED-RG:disk-red-rs) Res property name: Zpools
(CAL-RED-RG:disk-red-rs:Zpools) Res property class: extension
(CAL-RED-RG:disk-red-rs:Zpools) Res property description: The list of zpoo
ls
(CAL-RED-RG:disk-red-rs:Zpools) Res property pernode: False
(CAL-RED-RG:disk-red-rs:Zpools) Res property type: stringarray
(CAL-RED-RG:disk-red-rs:Zpools) Res property value: <NULL>
(CAL-RED-RG:disk-red-rs) Res property name: FilesystemCheckCommand
(CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property class: extens
ion
(CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property description:
Command string to be executed for file system checks
(CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property pernode: False
(CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property type: stringa
rray
(CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property value: <NULL>
(CAL-RED-RG:disk-red-rs) Res property name: AffinityOn
(CAL-RED-RG:disk-red-rs:AffinityOn) Res property class: extension
(CAL-RED-RG:disk-red-rs:AffinityOn) Res property description: For specifyi
ng affinity switchover
(CAL-RED-RG:disk-red-rs:AffinityOn) Res property pernode: False
(CAL-RED-RG:disk-red-rs:AffinityOn) Res property type: boolean
(CAL-RED-RG:disk-red-rs:AffinityOn) Res property value: TRUE
(CAL-RED-RG:disk-red-rs) Res property name: GlobalDevicePaths
(CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property class: extension
(CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property description: The l
ist of HA global device paths
(CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property pernode: False
(CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property type: stringarray
(CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property value: <NULL>
(CAL-RED-RG:disk-red-rs) Res property name: FilesystemMountPoints
(CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property class: extensi
on
(CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property description: T
he list of file system mountpoints
(CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property pernode: False
(CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property type: stringar
ray
(CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property value: /opt/sh
aw /cal/shaw

Difference betwn shared address and logical hostname

Hello,
For cluster 3.2, could someone explain the diff betwn "clreslogicalhostname create" and "clressharedaddress create"? I thought the former was to share a logical hostname (depending on DNS to resolve to the ip address) betwn nodes, and the latter to share ip address (don't need to rely ip address resolution). But examples of the latter use a hostname and not an ip address, which leads to my confusion.
Thank you for clarifying this!

You've got things a little bit confused.
A logical hostname resource is an IP address (and associated hostname) that is placed in a fail-over resource group and used by the application(s) in that resource group. Such a resource group is resident on one node only and thus the IP address only exists, i.e. is plumbed in, on that cluster node too.
An example of such a service would be, say, an NFS service, with the IP address being the one you mount shares from. Alternatively, it could be an HA-Oracle database with the IP address being that of the listener that clients connect to.
A shared address resource is an IP address (and associated hostname) that is placed in a fail-over resource group but is used by applications in a scalable resource group. The shared address IP/hostname becomes a global IP address, such that it is physically plumbed in, e.g. on bge0:1, on the cluster node where the fail-over resource group is mastered and also plumbed in on the loopback interface, e.g. lo:2, of the cluster nodes that run the scalable services that depend on it.
An example of such a service would be a scalable web server, e.g. Apache or Sun Java Web Server, that is run on multiple cluster nodes at once and has requests load-balanced to them directly by the cluster. The scalable IP address would provide a single address that clients could use, yet the requests can be serviced by one of several nodes.
Hope that helps,
Tim
---

Failed to created RAID in WAE-7371-K9

hi all
we have cisco wae-7371-k9 , we wanna recreate RAID device using cd recovery. we booting on cd, and when we done with option numbers 2,3,5 succes but when we came on option 7, we cannot recreate RAID, it failed, following the log:
Installer Main Menu:
    1. Configure Network
    2. Manufacture flash (done)
    3. Install flash cookie
    4. Install flash image from network
    5. Install flash image from cdrom
    6. Install flash image from disk
    7. Recreate RAID device (WAE-674/7341/7371 only)
    8. Wipe out disks and install .bin image
    9. Exit (Eject and reboot)
Choice [0]: 7
Recreate RAID device option is selected
All disk data will be lost.
Are you sure you want to recreate RAID array? [n]: y
Saving random seed...
dd: opening `/state/random-seed': No such file or directory
No volume groups found
Controllers found: 1
All data in logical drive 1 will be lost.
Deleting: logical drive 1 ("")
Command completed successfully.
Controllers found: 1
A selected physical drive is not available for use.
Command aborted.
Failed to create RAID Logical drive. (1,2)
   MODEL: OE7371
   FLASH: found, directory validated
COOKIE: valid
   IMAGE: 4.3.5.7
FLASHDEV: /dev/sda
what's wrong with wae ?if we run command show disk detail, all hard disk detected
NO-HOSTNAME# sh disk det
RAID Physical disk information:
disk00: Ready                      6SJ5Q4L8    286102 MB
disk01: Ready                      JTWSEBWL    286102 MB
disk02: Ready                      JTX0VYRL    286102 MB
disk03: Ready                      JTX1470L    286102 MB
disk04: Ready                      JTX1B9SL    286102 MB
disk05: Ready                      JTX1B24L    286102 MB
RAID Logical drive information:
Mounted file systems:
MOUNT POINT      TYPE       DEVICE                SIZE     INUSE      FREE USE%
Disk encryption feature is disabled.
can you help, what's the problem .?
is chassis or HDD error?

Budi,
Please turn off the unit, make sure you reseat the disks and then try the CD-recovery in the following way:
2,3, 5,8,7,8, remove the disk and 9
Please log the session then we can see how it went
Hope this helps!
Jorge

Failed while creating virtual Ethernet switch. Failed to connect Ethernet switch port

Hello Folks
I am completely stuck with the configuration of my virtual networks. I have one logical switch left to add to one of my Hyper-V 2012 R2 hosts when I started getting the error below when I try to add logical switches to either Hyper-V Host. I have been using
the document. 'Hybrid Cloud with NVGRE (Cloud OS)' to implement the virtual networking. Basically using the exact configuration that is in the document. I have added the PA Logical Network and the Network adapters and added the logical switch for it to my
hyper-v 2012 R2 host and everything was fine. I am now trying to add my ISCSI Logical Switch to the host and this is the error I get. My other Hyper-V host I get this error for any logical switch I am trying to add. Can someone help me with this error. I haven't
been able to find any information about it.
Also a some quick info on tracing an error like this so I can figure out what is causing it.
Thsi is my configuration so far
So as far as I know everything is peachy untill the error below. Dead stop now
Error (12700)
VMM cannot complete the host operation on the 08-NY-VHOST01.accounts.ccac-ont.ca server because of the error: Failed while creating virtual Ethernet switch.
Failed to connect Ethernet switch port (switch name = '******', port name = '88C16766-ED02-4AC0-8CD7-660AC9D424DD', adapter GUID = '{FAF431D8-0124-4E40-BB3B-9234BAA02973}'): The system cannot find the file specified. (0x80070002).
Unknown error (0x800b)
Thank you for your time
Christopher
Christopher Scannell

notice your GUID? you may want to consider ensuring that is the same GUID associated in your database. Sometimes during data corruption theres a smidge of a chance your sql database kind of either pulls old guids esp if this was reverted to snapshot
without it being powered off etc.
I would try that first. then i would consider if you get to configure that with your current liscense associated with the host. I would need way more info to help any further

Problems registering Logical Hostname resource

I�m trying to mount a HA Oracle.
I installed SC 3.1, with Volume Manager I configurated the logical devices.
I install Oracle 9i in the local HD of the cluster nodes.
I have 2 280R in the cluster.
I installed HA for Oracle from SC 3.1 Cd.
I configure in /etc/hosts in both nodes:
node 0:
/etc/hosts
<IP> bbddtlatam
node 1:
/etc/hosts
<same IP> bbddtlatam
I configure a IPMP for each interface (both machines)
# ifconfig qfe0 group iptest
and
#scrgadm -a -t SUNW.oracle_server
#scrgadm -a -t SUNW.oracle_listener
#scrgadm -a -g resource_name_group
but
when i try to register the logical hostname:
#scrgadm -a -L -g resource_name_group -l bbddtlata
Call to rpc.fed failed for resource bbddtlatam, method hafoip_validate.
Validation of resource bbddtlatam in resource group bbdd-ora-rg on node latamint-9 failed.
In /var/adm/messages
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 115461 daemon.error] in libsecurity __rpc_get
localuid failed
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 991800 daemon.error] in libsecurity transport
tcp is not a loopback transport
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 299417 daemon.error] in libsecurity strong Un
ix authorization failed
Jun 15 10:31:46 latamint-9 Cluster.RGM.rgmd: [ID 217093 daemon.error] Call failed: FE_RUN: RP
C: Authentication error; why = Client credential too weak
Jun 15 10:31:46 latamint-9 Cluster.RGM.rgmd: [ID 581180 daemon.error] launch_validate: call t
o rpc.fed failed for resource <bbddtlatam>, method <hafoip_validate>
Any idea????
Thanks.....

looking at your error
this all comes and looks like error with rpc
see if rpc deamon is running fine

Logical Hostname

Hi All ,
Below is my requirement
1) Two - Node Cluster
2) To Create Failover NFS resource group
I want to create a logica hostname resource, what is procedure and requirements for configuring the logical hostname.
I am very much confused in creating a logical hostname resource.
Please help to create a logical hostname.
Regards,
R. Rajesh Kannan.

Have you looked att he example in http://docs.sun.com/app/docs/doc/819-2979/z4000275997776?a=view
I would have thought that was fairly clear. If not, which specific bit do you need explaining?
Thanks,
Tim
---

Sun Cluster 3.1 Failover Resource without Logical Hostname

Maybe it could sound strange, but I'd need to create a failover service without any network resource in use (or at least with a dependency on a logical hostname created in a different resource-group).
Does anybody know how to do that?

Well, you don't really NEED a LogicalHostname in a RG. So, i guess i am not understanding
the question.
Is there an application agent which demands to have a network resource in the RG? Sometimes
the VALIDATE method of such agents refuses to work if there is no network resource in
the RG.
If so, tell us a bit more about the application. Is this GDS based and generated by
Sun Cluster Agent Builder? The Agent Builder has a option of "non Network Aware", if you
select that while building you app, it ought to work without a network resource in the RG.
But maybe i should back up and ask the more basic question of exactly what is REQUIRING
you to create a LogicalHostname?
HTH,
-ashu

Activate Logical Ports Fails with UDDI error

Hi experts....
I have run into another issue with the installation/configuration of DUET Enterprise. I see the following error in the SOA Manager on the SCL (under Service Administration --> SOA Configuration Request Queue Management):
Activate logical ports for service group /IWCNT/BPC_SERVICE_GROUP and application PS_ECQ_500/APPL_ECQCLNT500 in scenario DUET_STARTER_SERVICES_ALL: FAILED
When I drill down the lowest level errors are:
Failed to create a logical port using Service Registry
UDDI error: No Primary Services Registry maintained in this System.
Could not determine service using UDDI query
When I look in SOA Manager --> Global System Settings --> Service Registry on the SCL system there are no Services Registry defined....
Can anyone help? Do I need to somehow create a Services Registry?
Thanks in advance,
Simon
Edited by: Simon Kemp on Apr 6, 2011 12:26 AM

Hi Simon,
most likely there was an error when releasing the Services on the backend system (following the instructions of Note 1480794).
In order to solve this issue take a look not at the UDDI Error, but at the WSIL error ("Failed to create logical port using WSIL" -- since we are not using SLD to look-up the provider services on the backend, but the WSIL URL).
I have send you a Troubleshooting Guide that is currently being published on SDN. Can you check the chapters
7. An unexpected error occurred while executing the specified Action
18. When opening a Workspace in the Start Services scenario you get an unexpected error occurred
in it?
Regards,
Holger.

Restrict HA-NFS to logical hostname resource

I have a 2 node cluster running 2 HA-NFS pools (one active on each node at a time). The two nodes each have a connection to our storage network (a private network, but not the same as the cluster interconnect networks). They also each have connections to the public network.
I have everything working fine from a clustering standpoint. However, when I try to connect to the logical hostname of one of either of the NFS resource groups from FreeBSD, things fail. When I did a snoop, I saw the FreeBSD box talking to the address defined by my logical hostname for that resource group, then all of a sudden, the cluster node responding with its non-cluster address from that interface. As a result, the FreeBSD machine apparently rejects the packet, since it came from a differing source (despite it being UDP). Is it possible to restrict the NFS traffic to just the logical hostname for the resource group?
For example:
dfshares <clusternode> would return nothing, as the cluster node has no shares specifically listed.
But
dfshares <resourcegroup-lh-rs> would return the shares for that resource group.
Basically, can we bind SUNW.HA-NFS to a specific interface/address like we can with samba?

Hi,
1. Have a look at http://blogs.sun.com/SC/entry/why_a_logical_ip_is , which should explain part of the problem. I doubt that you can configure the NFS server to listen on a specific interface or address only.
2. I am not sure why your NFS client refuses the response from the NFS server. Or is it some firewall on your system that does this?
3. If you switch NFS to TCP, this "problem" should not occur.
Regards
Hartmut

Logical Hostname fail to create

Similar Messages

Maybe you are looking for