Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2187

May 14th, 2010 01:00

Cannot enable rule after restore

hi, all,

After I install AutoStart 5.3.SP3, I put my backup.def to the directory "C:\Program Files\EMC\AutoStart\ENvPlus\bin", while ENvPlus is the domain name I created during installation.

Then I ran the command "ftcli –domain ENvPlus –cmd restore & ftcli –domain ENvPlus –cmd “enableRule SysStateRule”"

SysStateRule is the rule I created in the backup.def.

Then the configuration was successfully done and the rule and other objects are created successfully, but the rule wasn't enabled, and I got the following error:

No AutoStart Primary Agents were found that would accept our connection.

Connection Unsuccessfully attempted at:

cnnms501

I think this is because when the "enableRule SysStateRule" is ran, the agent was restarted, but I'm not sure. Can anyone assure this?

Will the restore command lead to the agent restart?

Since this command works well in Legato 5.1, and the rule was enabled after the script ran, or after the agent is restarted.

Is there some workaround to this problem?

May 14th, 2010 01:00

Greetings,

I am out of the office and unavailable the week of Monday 10-May-2010

through Friday 14-May-2010. I will return Monday, 17-May-2010.

If assistance is needed with an existing service request please contact

support by phone at 1-877-534-2867 and the next available Technical

Support Engineer will be able to assist you.

If this is a new symptom, please don't hesitate to open a new case by

phone at 1-877-534-2867 or via the Powerlink web site at

http://powerlink.emc.com.

Best Regards,

Daniel

157 Posts

May 14th, 2010 02:00

Hello again - no, the agent should not restart after the import of the backup .def file. For some reason it was down when you issued the enableRule command. Check the log file for the possible cause.

79 Posts

May 14th, 2010 02:00

Thanks for your reply.

After the Agent restarted, I can enable the rule manually. So is it possible the problem is with the backup.def?

I've checked the file "autoRecover.log" under "C:\Program Files\EMC\AutoStart\ENvPlus\log\agent", the content is as follows:

Running auto-recover script.
Backbone has failed. Restarting Agent.
Complete.
there is one file "MirrorUnconfig.log" under this directory with the following context.
.\MirrorConfig: output will be redirected to ../log/agent/MirrorUnconfig.log
rip=(null) rmn=(null) lip=(null) lmn=(null) dmn=ENvPlus fop=../log/agent/MirrorUnconfig.log
.\MirrorConfig: getKeyAndValue getting SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\IPAddr
.\MirrorConfig: getKeyAndValue succeeded opening SYSTEM\CurrentControlSet\Services\VncTransport\Parameters
.\MirrorConfig, getKeyAndValue: RegQueryValue query SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\IPAddr returned
.\MirrorConfig: registry key SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\IPAddr read (, size 1)
.\MirrorConfig: getKeyAndValue getting SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainLocalNode
.\MirrorConfig: getKeyAndValue succeeded opening SYSTEM\CurrentControlSet\Services\VncTransport\Parameters
.\MirrorConfig, getKeyAndValue: RegQueryValue query SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainLocalNode returned
.\MirrorConfig: registry key SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainLocalNode read (, size 1)
.\MirrorConfig: getKeyAndValue getting SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\RemoteIPAddr
.\MirrorConfig: getKeyAndValue succeeded opening SYSTEM\CurrentControlSet\Services\VncTransport\Parameters
.\MirrorConfig, getKeyAndValue: RegQueryValue query SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\RemoteIPAddr returned
.\MirrorConfig: registry key SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\RemoteIPAddr read (, size 1)
.\MirrorConfig: getKeyAndValue getting SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainRemoteNode
.\MirrorConfig: getKeyAndValue succeeded opening SYSTEM\CurrentControlSet\Services\VncTransport\Parameters
.\MirrorConfig, getKeyAndValue: RegQueryValue query SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainRemoteNode returned
.\MirrorConfig: registry key SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainRemoteNode read (, size 1)
.\MirrorConfig: getKeyAndValue getting SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainName
.\MirrorConfig: getKeyAndValue succeeded opening SYSTEM\CurrentControlSet\Services\VncTransport\Parameters
.\MirrorConfig, getKeyAndValue: RegQueryValue query SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainName returned
.\MirrorConfig: registry key SYSTEM\CurrentControlSet\Services\VncTransport\Parameters\AAMDomainName read (, size 1)
.\MirrorConfig: domain name not REG_MULTI_SZ format - converting...
.\MirrorConfig: no domain names currently in registry
.\MirrorConfig, domain name (ENvPlus) not found in registry

May 14th, 2010 02:00

Greetings,

I am out of the office and unavailable the week of Monday 10-May-2010

through Friday 14-May-2010. I will return Monday, 17-May-2010.

If assistance is needed with an existing service request please contact

support by phone at 1-877-534-2867 and the next available Technical

Support Engineer will be able to assist you.

If this is a new symptom, please don't hesitate to open a new case by

phone at 1-877-534-2867 or via the Powerlink web site at

http://powerlink.emc.com.

Best Regards,

Daniel

157 Posts

May 14th, 2010 02:00

Ah, the error is caused by the fact that the EMC Mirror Data Sources do not get completely recreated when importing the backup file. That s because the mirror data source and corresponding services store the confguration in the registry. Importing the backup file recreates the configuration of the data sources in Autostart config, but not the registry part. Unfortunately these data sources have to be recreated manually. It still should no cause the backbone to restart at least from my experience.

May 14th, 2010 02:00

Greetings,

I am out of the office and unavailable the week of Monday 10-May-2010

through Friday 14-May-2010. I will return Monday, 17-May-2010.

If assistance is needed with an existing service request please contact

support by phone at 1-877-534-2867 and the next available Technical

Support Engineer will be able to assist you.

If this is a new symptom, please don't hesitate to open a new case by

phone at 1-877-534-2867 or via the Powerlink web site at

http://powerlink.emc.com.

Best Regards,

Daniel

May 14th, 2010 02:00

Greetings,

I am out of the office and unavailable the week of Monday 10-May-2010

through Friday 14-May-2010. I will return Monday, 17-May-2010.

If assistance is needed with an existing service request please contact

support by phone at 1-877-534-2867 and the next available Technical

Support Engineer will be able to assist you.

If this is a new symptom, please don't hesitate to open a new case by

phone at 1-877-534-2867 or via the Powerlink web site at

http://powerlink.emc.com.

Best Regards,

Daniel

79 Posts

May 14th, 2010 05:00

Thanks for your timely reply!

After the AutoStart is installed, the "MirrorUnconfig.log" is there.

I use one backup.def configured by us own to restore the AutoStart configuration.

After investigation, I found out that the agent restart was caused by the misconfiguration of the backup.def.

There is one field called nodefd, after I wrote the IP address of my PC to the "source.addr" field, then after restore, the agent wasn't restarted.

nodefd server1{

  nodeAddrs = {
    {
      sourceType = domain
      source.addr = 172.21.1.153
      destination.addr =
    }
    {
      sourceType = domain
      source.addr = 172.21.1.153
      destination.addr =
    }
  }
  mirrorInfo.address =
  mirrorInfo.partner.nodeName =
}
So I want to ask one question, is anyone know the what does this field relate with? Is it specify the NIC IP of my PC? How will this field affect the AutoStart behavior? Is there corresponding field in the console?

May 14th, 2010 05:00

Greetings,

I am out of the office and unavailable the week of Monday 10-May-2010

through Friday 14-May-2010. I will return Monday, 17-May-2010.

If assistance is needed with an existing service request please contact

support by phone at 1-877-534-2867 and the next available Technical

Support Engineer will be able to assist you.

If this is a new symptom, please don't hesitate to open a new case by

phone at 1-877-534-2867 or via the Powerlink web site at

http://powerlink.emc.com.

Best Regards,

Daniel

79 Posts

May 15th, 2010 05:00

In Legato5.1 we didn't set the IP here, but the backup.def can be well restored without restart.

do you know the difference in Legato5.1 and AutoStart 5.3?

79 Posts

May 15th, 2010 07:00

After several times test, I found if I delete the Nodefd {} filed in my backup.def, then the restore won't let the agent restart.

Also I export the domain information before and after I restore my backup.def to two files, I found the Nodefd() field were the same.

Now I want to ask you one question, if I didn't set this filed, if there will be some problem?

And is there some difference effect to the Domain between not setting the Nodefd{} field and setting the Nodefd{} as the following?

nodefd cnnms501 {
  nodeAddrs = {
    {
      sourceType = domain
      source.addr =
      destination.addr =
    }
    {
      sourceType = domain
      source.addr =
      destination.addr =
    }
  }
  mirrorInfo.address =
  mirrorInfo.partner.nodeName =
}
No Events found!

Top