Solutions

Substitution variables should not contain spaces and "@(" should have a corresponding closing parenthesis

Solutions ID:    KB3773
Version:    4.0
Status:    Published
Published date:    04/16/2010
Updated:    07/13/2011
 

Problem Description

Using this syntax in a overlay file, as  below, manifests with  this error -  "Substitution variables should not contain spaces and "@(" should have a corresponding closing parenthesis".  

ftp-client primary password "xyz@111


Typing the command in at the cli prompt of the proxysg works, but not though the Director Management Console. 

 Is there a workaround that the Director will understand so I do not have to manually login int to all  my  200+ ProxySG to type in this command?

 

Resolution

This is a known issue detected SGME versions prior 5.3.1.2.  On these versions,  Director failed to process any overlay files  that contained the @ (at) symbol. These versions of Director interpreted the @ symbol as the start of a substitution variable.

NOTE: This issue is fixed on SGME 5.3.1.2 or later, and is documented on SGME 5.3.1.3 release notes. 

If you cannot perform the necesary SGME upgrade at the moment, you may work around this issue by actually using substitution variable to replace password value (xyz@111), and specifying this password value as substitution variable for one or many devices. For example:

ftp-client primary password @(ftppassword)


In Device Specific Settings (Configure Tab, righ-mouse click on a device > Edit, bottom of the Edit Device window > Advanced Settings > Substitution Variables > New; For Substitution Variable Name type: ftppassword, For Value type: xyz@111)

This example works well if you need to have a particular value added to a particular device, you can also use CSV file and import the value to many devices. In order to do the import use GUI File menu > Import Substitutions; on second screen of the wizard (“Import” screen).

NOTE: For details on how to upgrade your SGME versions, see these articles.

Upgrade path- FAQ1172

How to upgrade - KB1425

 


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question