[urgent]listResourceGroup does not work in AutoStart 5.4

Hi,

Did you install an cumulative hotfix?

It seems that this is a defect.

I'm sorry.

I was able to display it correctly in the environment of AutoStart5.4.

--------------------------------------------------------------------------------------

C:\Program Files\EMC\AutoStart\eas54\bin>ftcli

                            Welcome to EMC AutoStart
                            Version 5.4.0 build 173
           Copyright 1998 - 2010 EMC Corporation. All rights reserved

AutoStart> lrg
    Group              State            Node        Start/Stop Time            Monitoring State
----------------  ---------------  --------------   ---------------            ----------------
OW_ora10g         Online Pending   ora1             Thu Feb 24 22:49:03 2011   Enabled

--------------------------------------------------------------------------------------

Build 195 was a same result.

At present, the trouble has not occurred in my environment.

thank you, I will check the my 5.4 build version when I am back to lab.

My AutoStart5.4 is downloaded from PowerLink. Is there new cumulative hotfix?

Hi,

Mr. Ito is correct, this is not a known defect in AutoStart.  The listResourceGroup (lrg) command should work fine in AutoStart 5.4.

You are actually getting legitimate output from the command.  The RG is in an Unknown state, which is a legitimate state you can get into.  Not exactly sure how you got here?  Normally this state is seen if the node running the RG is in an Agent Failed state, i.e. the node where you ran this command sees the other node as Agent Failed (which implies that the AutoStart Agent process/service is not running).  The Unknown state prevents this node from taking any action on the RG.  The assumption being that the Agent is down, but the RG may still be running fine.  The Agent may actually be not running or possibly there is a communication issue between the nodes, and this node's Agent cannot talk to the other node's Agent.

Normally if the Agent is restarted on that node with the RG, he will verify the status of the RG and Resources on startup, then change the state appropriately away from Unkown.  Another item that can change the Unknown state, is if that node with the RG goes into the Node Failed state, then the surviving node will then change the state of the RG from Unknown to Failed and take the appropriate action per the configuration.

You'll have to dig into the situation a bit deeper to determine what is really going on.

I'd suggest checking the process states and running the ftcli command listNodes (ln) on all AutoStart nodes, to get a clear picture of how they see each other.

Hope this helps out.

Best Regards,

Daniel Vongehr

EMC Technical Support

Hello,

Yes, there is a new AutoStart Cumulative Hot Fix for 5.4 on Windows.

It is available on Powerlink via  Support -> Software Downloads and Licensing -> Downloads A-B -> AutoStart

It should be at the top of the page, dated February 7, 2011.

It is in relation to a technical advisory which you can reference here: EMC Technical Advsiory (ETA) - AutoStart

While this Cumulative Hot Fix does not address anything related to ftcli and the lrg command, it is recommended that you apply it on your 5.4 installations.

Let me know if you have any further questions.  Happy to help out.

Best Regards,

Daniel Vongehr

EMC Technical Support

Hello,

Following are my further test results

• Test1

• Test2

But for the same server, following commands can not work

C:\Documents and Settings\EnvisionPlusUser>"C:\Program Files\EMC\AutoStart\envpl

us\bin\ftcli" -domain envplus -connect localhost -port 8042 -cmd listResourceGroups

    Group              State            Node        Start/Stop Time            Monitoring State

----------------  ---------------  --------------   ---------------            ----------------

rg_id_1           Unknown                                         Invalid State

                  Unknown                                         Invalid State

• Test3

C:\Documents and Settings\EnvisionPlusUser>"C:\Program Files\EMC\AutoStart\envpl

us\bin\ftcli" -domain envplus -connect localhost -port 8042 -cmd listProcs

Name                             State      Active On Node

---------------------------------------------------------------

cnsqaenvision20                  stopped

EriEnvDbExt                      stopped      cnsqaenvis  Sat Feb 26 06:56:17 2011

EriEnvEventLog                   stopped      cnsqaenvis  Sat Feb 26 06:56:27 2011

EriEnvRM                         stopped      cnsqaenvis  Sat Feb 26 06:47:56 2011

MSSQLSERVER                      stopped      cnsqaenvis  Sat Feb 26 06:56:37 2011

SQLSERVERAGENT                   stopped      cnsqaenvis  Sat Feb 26 06:56:32 2011

• Test4

C:\Documents and Settings\EnvisionPlusUser>"C:\Program Files\EMC\AutoStart\envpl

us\bin\ftcli" -domain envplus -connect localhost -port 8042 -cmd listNodes

        Node              Type              State

-----------------------  ------------    --------------

  cnsqaenvision20        Primary      Agent Running

AutoStart Agent is started and it has pemanent license. So there is no problem with AutoStart agent -- Test1, Test3 and Test4 can return the right results.

For Test2, Test3 and Test4, they run in the same way. listProcs and listNodes can work but listResourceGroups can not.

But for Test1 and Test2, any difference between them? 8042 port should work because Test3 and Test4 are right.

When the hotfix AT_EAS540_WIN_x86 is patched, the results are the same to the above.

One more I want to point out that these servers are upgraded from AutoStart 5.3SP3 to 5.4.

Servers upgraded from AutoStart5.3SP3/5.1.2 and fresh installation of AutoStart 5.4 have the same problem.

Thanks

I see how to reproduce this problem now. I is caused by "-connect localhost"

1. remove "-connect localhost", it can work well
2. change localhost to IP -- "-connect 172.21.7.20", it can work well
3. change localhost to node name -- "-connect cnsqaenvision20", it can work well

I sill confused that why "C:\Program Files\EMC\AutoStart\envplus\bin\ftcli" -domain envplus -connect localhost -port 8042 -cmd lrg can not work?

From ftcli command description,

It should specify the node name, but why 5.3 and legato 5.1 can work well to connecto to "localhost"??

Hi,

Your test is correct.

However, it is not a issue that it cannot be connected in LOCALHOST.

You should replace it with IP or Host Name.

This is not a serious impact.

In addition, I think that it is not a defect.

Because please look at Help of the command.
It is a rule that specifies the Node Name.

But

Why listNodes and listProcs can work for LOCALHOST in 5.4?

Why listResourceGroups can work for LOCALHOST in 5.3SP3?

It will take us a lot of time to find such minor differences.

Hi,

LOCALHOST can be used in a certain command.
It is correct.

However, you should replace all the commands that you use with Node Name.

It will be resolved in this issue.

Yes, we know how to resolve this problem when we find it related to LOCALHOST.

But more root cause description is necessary because we need to provide it to our own customers -- AutoStart is integrated into our products and deliverd to our customers.

Thanks