Forum Discussion

MIG31's avatar
MIG31
Level 4
12 years ago

how to probe resources

[root@system1]# /opt/VRTSvcs/bin/hastatus -sum                  
-- SYSTEM STATE
-- System               State                Frozen

A  system1       RUNNING              0
A  system2       RUNNING              0

-- GROUP STATE
-- Group           System      Probed     AutoDisabled    State        

B  ClusterService  system1       Y          N               ONLINE       
B  ClusterService  system2       Y          N               OFFLINE      
B  appsGroup       system1       N          N               PARTIAL      
B  appsGroup       system2       N          N               OFFLINE      
B  vxfen           system1       Y          N               OFFLINE      
B  vxfen           system2       Y          N               OFFLINE      

-- RESOURCES NOT PROBED
-- Group           Type                 Resource             System             

E  appsGroup       IP                   SysIP                system1     
E  appsGroup       IP                   SysIP                system2     
E  appsGroup       Mount                mntGroup             system1     
E  appsGroup       Mount                mntGroup             system2     
E  appsGroup       NIC                  SysNIC               system1     
E  appsGroup       NIC                  SysNIC               system2     
 

cant get my SysIP online because the resource has not been probed how do you probe the appsgroups in bold

thanks

mig31

  • Hi, MiG

     

    NIC resource not probed,  need check if device name is right in your configuration.

    ifconfig -a   check if nic device is there and plumbed.

     

    for IP resource,  check if ip is online, by check ifconfig -a, netstat -in.

     

    for mount resource, check df -k  output, mount -v output, if file system has mounted.

     

    Or you can paste output of:

    1. hares -display

    2.ifconfig -a

    3.df -k

    4. netstat -in

     

    For help you check.

  • Agree with what Mike has said above, with one exception:

    you have set PrefixLen for SysIP to 1000

    SysIP        PrefixLen             global         1000

    This is not a valid value. Per bundled agents guide (eg: https://sort.symantec.com/public/documents/sfha/6.0.1/solaris/productguides/html/vcs_bundled_agents/ch03s02s05.htm )

    PrefixLen
    This is the prefix for the IPv6 address represented as the CIDR value.
    When you use the IPv6 protocol, you must configure values for this attribute and the corresponding NIC agent's Device and Protocol attributes.
    Type-dimension: integer-scalar
    Range: 1 - 128
    Example: 64

    Suggest setting the attributes Mike has pointed out above, if you still have issues then check the Bundled Agents guide to ensure you haven't missed anything else.

  • Hi MIG31,

    From the main.cf could clearly find out the reason why SysIP and SysNIC not probed, which does like why the mnt resource not probe. There is no netmask for IP and no device for NIC. 

    And since you use bond0 for SysIP too as WebIP, configure a proxy resource of SysNIC is proper way.

    So change the configuration to this :

            IP SysIP (
                    Device = "bond0"
                    Address = "10.152.179.8"

                    NetMask = "255.255.255.0"
                    )

          Proxy SysNIC (

                  TargetResName = csgnic

                 )

         SysIP  requires SysNIC

     

    You don't need to configure bond0:0 in the main.cf, system will configure it as bond0:0 automatically.

  •  

    RESOURCES NOT PROBED can be mean:

    1. Resource are not probed because resource is disabled.
    2. Resouce probe failed to run properly because resource is not configured properly - like attribute missing.
    3. Application not configured properly - like missing mount point or application not installed yet.

    Note if the wrong attributes are specified, the probe is quite often successful - in that it reports offline as oppose to unknown (NOT PROBED) and so if you had specified a Device for your NIC and it was wrong, then I THINK VCS would have reported it as offline as oppose to NOT PROBED.

    The issue in this case appears to be 2 as mandatory attributes were not specified.

    Mike

  • Hi Mike, Stinsong, g_lee thanks for your support I was swamped yesterday, i could not respond to your replies I am sorry

    Mig31

  • Thanks, Mike sorry for not responding to your reply it really helped me

    Thanks,

    MIG31

     

  • g_lee thanks for support sorry i was swamped yesterday i couldnt reply on your comments

    Thanks

    MIG31