No error message is displayed.
SMA 7.5 SP1 Linux is not compatible with SSRL Plug-in. This issue is caused because of SSRL Plug-in registration failure, which results into deadlock state.
The issue is observed in the following scenarios:
Scenario 1: When new 32-bit/64-bit Linux clients are being managed by installing SMA Linux and SSRL Plug-in from SSRMS 2013 R2 (on SMP 7.5 SP1).
Scenario 2: You upgrade the SSRMS 2011/2013 Server to SSRMS 2013 R2 and SMP is upgraded to 7.5 SP1. After the SSRMS and SMP upgrades, you upgrade SMA Linux agents on the managed client and then try to upgrade the SSRL Plug-in.
Scenario 3: You install 64-bit SMA 7.5 SP1 agent (not supported by SSRL) on the managed Linux Client and try to push SSRL Plug-in.
Solution for Scenario 1:
Solution Scenario 2:
a. Open Symantec System Recovery 2013 R2 Management Solution console and go to Install the Symantec Management Agent page.
b. Under the Installation Setting page, manually select the 32-bit Agent. (Select the Manually select OS type option even for 64-bit client computers).
c. Click Install to upgrade the agent.
a. Launch Symantec System Recovery 2013 R2 Management Solution.
b. Follow steps 3 and 4 mentioned in the Solution Scenario 1 section.
c. Go to Packages and Polices > expand Upgrade Policies > under Agent Plug-in > select Upgrade Plug-in for Symantec System Recovery for Linux to upgrade the Linux Plug-in and send the upgrade plug-in policies for the client.
d. Go to Install Policies > Under Symantec System Recovery Linux Edition > 2013 R2 > Select Install Without User Interface to upgrade Symantec System Recovery for Linux.
Solution Scenario 3:
a. Copy and unzip the attached SMP 7.5 SP1.zip file to a Linux client machine.
The zip file contains the following:
o agent.sh
o config.txt
o main.sh
b. Update the config.txt file with the credentials of the Linux client machines, which are in deadlock because of 7.5 SP1 Agent and SSRL plug-in registration failure.
Example:-
0
(There should not be empty line between the entries and last line should be zero)
c. Change the file mode by running the following command:
Chmod +x main.sh
d. After updating the config.txt file, run main.sh.
Note: For the scripts to run, the Linux computer must have the expect rpm available. If the expect rpm is not available, you can find the rpm in the Linux ISO file and install it.
Note: The Linux computer, on which you run main.sh, should be able to communicate with all the other Linux computers where the deadlock occurred.
a. Launch Symantec System Recovery 2013 R2 Management Solution.
b. Uninstall the 64-bit SMA agent installed on the client machine.
c. Follow the Steps 2 to 8 mentioned in the Solution Scenario 1 section.
Perform the following steps to avoid an SMA agent deadlock in the SMP upgrade scenario. The SSRMS 2013 R2 is installed on SMP 7.5 platform and have managed clients with SMP Linux agent 7.5, SSRL Plug-in, and SSRL 2013 R2 installed.
Applies To
Server: Symantec Management Platform 7.5 SP1 or later with Symantec System Recovery 2013 R2 Management Solution and Symantec System Recovery 2013 R2 Linux Management Solution installed.
Clients: All supported Linux clients.
Note: To manage Linux clients on Symantec Management Platform 7.5 SP1, upgrade to HF4 or later versions to implement the solutions mentioned in this article.
Note: To manage 64-bit Linux clients, you must install 32-bit SMA Linux agent only.