VIP variable usage in Management Center VPM (reflect IP)

I need a solution

Hello,

I have a question regarding proxys’ reflect IP configuration from Management Center. I would like to install a VPM policy from a MC to multiple proxys using the VIP of each of them (this ip is different in each proxy). The thing is, is it possible to configure some variable from the MC that uses each proxy’s VIP?

I have done some research and I have only seen these variables:

Management Center —> Use Substitution Variables in Policies and Scripts
 

https://origin-symwisedownload.symantec.com//resources/webguides/managementcenter/2.0.1.1/ManagementCenter.htm#ConfigurationManagementGuide/6_Scripts/variable_substitution.htm

Policy CPL —> Use Substitution Variables in Policies and Scripts

https://origin-symwisedownload.symantec.com/resources/webguides/managementcenter/1.8.1.1/Content/ConfigurationManagementGuide/6_Scripts/variable_substitution.htm#supp_var

Best Regards,

0

Related:

  • No Related Posts

RP4VM 5.1.1.15 upgrade to 5.2

Hi,

Yes, going from 5.1.SP1.P5(d.246) to 5.2P1 (rel5.2.P1_a.362_release_emc_md5_1bb251ae2f6a2c5f5efb57a68b718b61_RP4VMs)



and nothing non standard with the deployment

example of mod file….

{

“1”: {

“modifiedTweaks”: [

{

“tweakName”: “t_defaultNetworkSecurityLevel”,

“value”: “SECURITY_LEVEL_NON_SECURE”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_isIPSplitterDefault”,

“value”: “false”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_isIPSplitterDefault”,

“value”: “true”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_shouldEnableIOF”,

“value”: “false”,

“modifierName”: “Cluster Logic(5.1)”

}

],

“ranSignedScripts”: []

},

“2”: {

“modifiedTweaks”: [

{

“tweakName”: “t_defaultNetworkSecurityLevel”,

“value”: “SECURITY_LEVEL_NON_SECURE”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_isIPSplitterDefault”,

“value”: “false”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_isIPSplitterDefault”,

“value”: “true”,

“modifierName”: “Cluster Logic(5.1)”

},

{

“tweakName”: “t_shouldEnableIOF”,

“value”: “false”,

“modifierName”: “Cluster Logic(5.1)”

}

],

“ranSignedScripts”: []

}

}

Cheers

Dave

Related:

Re: scini volume I/O error – failed getting LB-Info

Hi iemmanuylov,

In a case like this, it would be difficult to give a complete answer without logs to review. The LB-Info error you are referencing is basically saying that it could not get the logical block information, in this case because the SDS_ID came back as 0. Meaning, there was IO (read/write) that was attempted and it could not be completed because there was no valid SDS to fulfill the request.

What you would be looking for is in the MDM/SDS logs, something to correlate to the timestamps above as to what was going on at the time. If you can’t find anything or need root cause, the suggestion after that would be to open a support ticket and let the ScaleIO engineers take a look.

Hope that helps,

Rick

Related:

  • No Related Posts