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
---

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

  • 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

  • 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

  • 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

  • RMAN script problem to create logical standby database !

    Dear Friends ,
    I am using Oracle10g database . I want to create a logical standby database . I create two database :
    Primary : orcl
    standby : orclsby1
    Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
    The script is below which I have to run in Primary (orcl) database :
    Script :
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'orcl','orclsby1'
    set db_unique_name='orclsby1'
    set db_file_name_convert='/orcl/','/orclsby1/'
    set log_file_name_convert='/orcl/','/orclsby1/'
    set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
    set log_archive_max_processes='5'
    set fal_client='orclsby1'
    set fal_server='orcl'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(orcl,orclsby1)'
    set log_archive_dest_1='service=orcl ASYNC
    valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
    Problem which I got :
    [oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
    Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: ORCL (DBID=1227832857)
    connected to auxiliary database: ORCLSBY1 (not mounted)
    RMAN> @cr_phys_sby1.txt
    RMAN> run {
    2> allocate channel prmy1 type disk;
    3> allocate channel prmy2 type disk;
    4> allocate channel prmy3 type disk;
    5> allocate channel prmy4 type disk;
    6> allocate auxiliary channel stby type disk;
    7> duplicate target database for standby from
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
    RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
    I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
    Both databases are running on Oracle10g platform .
    Waiting for ur kind reply .. ...

    You need to:
    - create a SPFILE manually for standby database
    - use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
    - remove all SPFILE statements from RMAN script.

  • Problem while creating logical port using soamanager

    Hi all,
    I have created a client proxy for web service from a 3rd party system.
    When i am creating a logical port for the same consumer proxy i get a error as follows:
    RABAX_STATE -e: UNCAUGHT_EXCEPTION
    and a dump saying
    "  The exception 'CX_SXMLP' was raised, but it was not caught anywhere along the call hierarchy.
         Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program
          'CL_SXMLP_FRAGMENT=============CP' has to be terminated.                  
    Please suggest what can be done or what can be the problem.
    Thanks in advance.
    Komal

    Pls go to txn SM59 and check if the RFC destination for webservice is working in the test connection.
    Then go to txn LPCONFIG and create the logical port using the RFC dest.  Pls mention the path suffix appropriately.
    Next in your code while instantiating the client proxy pass the logical port name in the constructor (if the LP is not maintained as default).
    Pls reward points if the tips are helpful.

  • Strange Problem with creating logical Destination

    Hello experts,
    I have a really strange problem. I have created some AS and BO and deployed all web services. The problem is - where can i register the logical destination. Normaly the button should be under:
    NWA->Configuration Management -> Infrastrucure (SP1)
    But now I am using SP3 and I can't find the Button for WS Destinations. Is this now managed from another Button or is it not longer neccessary ????????
    How can I than integrate my operation from the BO in a Visual Composer DC.
    Thanks a lot
    Regards
    Marco

    hi,
    you could try the  nwa > SOA Management > Destination Template Management >
    best regards,
    v s

  • Problem while creating Logical System Connecting Portal to ECC (Backend)...

    Hi
    - I am trying to connect portal to ABAP so that from portal's iView i could access any ABAP T-Code (e.g. SE37).
    - Secondly, just wanted to let you know that i am not implementing SSO.
    - I used iView's SAP GUI Type = SAP GUI for HTML.
    I made following 3 tests, out of which ITS connection is failed. and while previewing my iView i m not able to connect with ABAP and giving error:  "The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error."
    Could u pls guide me what to do....  And i mentioned everything at the bottom in detail.
    Thanks & looking forwarded for your replies.....
    SAP Web AS Connection (Successful)
    Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
    Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (192.168.1.104:8001)
    5. The host name 192.168.1.104 was resolved successfully.
    6. The server 192.168.1.104 was pinged successfully.
    7. The Web AS ping service http://192.168.1.104:8001/sap/bc/ping was pinged successfully.
    8. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/bsp/sap was obtained successfully.
    ITS Connection (Failed)
    Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether the system object has a valid system alias
    4. Check whether a SAP system is defined in the system object
    5. Validate the following parameters: ITS protocol; ITS host name
    6. Checks if the host name of the server can be resolved.
    7. Pings the server to see if it is alive.
    8. Checks HTTP/S connectivity to the defined back-end application
    Results
    1. The system ID is valid
    2. The system was retrieved.
    3. Retrieval of the default alias was successful
    4. The system object represents an SAP system
    5. The following parameters are valid: ITS Protocol (http) ITS Host Name (192.168.1.104:8001)
    6. The host name 192.168.1.104 was resolved successfully.
    7. The server 192.168.1.104 was pinged successfully.
    8. User mapping is valid
    9. An HTTP/S connection to http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui/ was not obtained successfully; this might be due to a closed port on the Firewall.
    Test Connection with Connector (Successful)
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
    Results
    1. Retrieval of default alias successful.
    2. Connection successful.
    I am getting following error while Previeiwng iView.
    Error when processing your request
    What has happened?
    The URL http://192.168.1.104:8001/sap/bc/gui/sap/its/webgui was not called due to an error.
    Note
    The following error text was processed in the system D10 : Template interpretation cancelled, syntax error.
    The error occurred on the application server eccdcs1s_D10_01 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
          SYSTEM-EXIT of program SAPLSFUNCTION_BUILDER
          Function: RS_FUNCTION_INITIAL_SCREEN of program SAPLSFUNCTION_BUILDER
          Method: IF_WB_PROGRAM~PROCESS_WB_REQUEST of program CL_FB_FUNCTION_INITIAL_SCREEN=CP
          Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR===============CP
          Method: DO_THE_NAVIGATION of program CL_WB_NAVIGATOR_VIS_AS_DYNPRO=CP
          Method: PROCESS_WB_REQUEST of program CL_WB_MANAGER=================CP
          Method: PROCESS_REQUEST_QUEUE of program CL_WB_MANAGER=================CP
          Method: IF_WB_MANAGER~SET_WORKSPACE of program CL_WB_MANAGER=================CP
          Method: START_INTERNAL of program CL_WB_STARTUP=================CP
          Module: MANAGER_START of program SAPLWB_MANAGER
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the   system D10 in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server eccdcs1s_D10_01 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server eccdcs1s_D10_01 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 001 -u: SAPUSER -l: E -s: D10 -i: eccdcs1s_D10_01 -w: 0 -d: 20090924 -t: 202054 -v: RABAX_STATE -e: ITS_CANT_LOAD_INCLUDE
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Edited by: Harpal Singh on Sep 24, 2009 4:55 PM

    Hi,
    > Goto SE80, Select "Internet Service". Give service name as WEBGUI and enter. Right click on the WEBGUI and select Publish -  > Complete service.
    Source : http://wiki.sdn.sap.com/wiki/display/BI/BiAdminCockpit+Issues
    Or call transaction SIAC_PUBLISH_ALL_INTERNAL to publish all services.
    [Note 964521 - Short dump ITS_CANT_LOAD_INCLUDE w/ call of SAP GUI for HTML|https://service.sap.com/sap/support/notes/964521].
    Regards,
    Pierre

  • 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

  • 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
    ---

  • 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
    ---

  • 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".

  • Zone Cluster: Creating a logical host resource fails

    Hi All,
    I am trybing to create a logical host resource with two logical addresses to be part of the resource, however, the command is failing. Here is what I run to create the resource:
    clrslh create -Z pgsql-production -g pgsql-rg -h pgprddb-prod,pgprddb-voip pgsql-halh-rs
    And I am presented with this failure:
    clrslh: specified hostname(s) cannot be hosted by any adapter on bfieprddb01
    clrslh: Hostname(s): pgprddb-prod pgprddb-voip
    I have pgprddb-prod and pgprddb-voip defined in the /etc/hosts files on the 2 global cluster nodes and also within the two zones in the zone cluster.
    I have also modified the zone cluster configuration as described in the following thread:
    http://forums.sun.com/thread.jspa?threadID=5420128
    This is what I have done to the zone cluster:
    clzc configure pgsql-production
    clzc:pgsql-production> add net
    clzc:pgsql-production:net> set address=pgprddb-prod
    clzc:pgsql-production:net> end
    clzc:pgsql-production> add net
    clzc:pgsql-production:net> set address=pgprddb-voip
    clzc:pgsql-production:net> end
    clzc:pgsql-production> verify
    clzc:pgsql-production> commit
    clzc:pgsql-production> quit
    Am I missing something here, help please :)
    I did read a blog post mentioning that the logical host resource is not supported with exclusive-ip zones at the moment, but I have checked my configuration and I am running with ip-type=shared.
    Any suggestions would be greatly appreciated.
    Thanks

    I managed to fix the issue, I got the hint from the following thread:
    http://72.5.124.102/thread.jspa?threadID=5432115&tstart=15
    Turns out that you can only define more than one logical host if they all reside on the same subnet. I therefor had to create 2 logical host resources for each subnet by doing the following in the global zone:
    clrslh create -g pgsql-rg -Z pgsql-production -h pgprddb-prod pgsql-halh-prod-rs
    clrslh create -g pgsql-rg -Z pgsql-production -h pgprddb-voip pgsql-halh-voip-rs
    Thanks for reading :)

Maybe you are looking for

  • Kernel panic in Mavericks

    Hi, I haven’t found any help searching the forum and I’ve decided to post. I have a Macbook Pro that is having kernel panic almost any time I use it on the go. When it’s on my desk connected to the external monitor works like a clock, when I travel q

  • Levels adjustment layer.

    hello. ive been doing this simple tutorial for a image im working on. its creating a starry sky but when i get the desired effect in adjustment layers in wont save my effect. blank canvas--fill with black filter--noise 100% with monochromatic ticked.

  • Hi, i have doubt in alv field cat log

    1)In alv field cat preparation (i dont want to display for one particular field in output screen) can u pls send me the code. 2)in field cat for a particular field i want to display in different color for that can u send me code. 3)code for (DOUBLE C

  • Need a clear answer on how to enforce Standard CALs usage.

    I found a few related threads and Blog post but no clear answer. Most of my users will have a standard CAL and I need to lock them down so they can only use those features. I need a clear and concise way to do this and it looks like MS is unwilling t

  • Sender Soap

    Hi all, im facing a doubt. i have a sender soap interface but the customer give to me the wsdl.so what can i do? i allways define de WSDL in PI for sender SOAP. but in this case i already have the wsdl. so what can i do? Thanks Rodrigo