000029157 - How to Manually Upload Files and Recreate the Securty Analytics 10.X YUM Repository

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000029157
Applies ToThis procedure applies to all Security Analytics  10X servers that supports yum updates.  This procedure is to be performed only on the SA Server itself, not on individual component hosts.
IssueThis procedure can be used when the SA repository does not contain the necessary files to upgrade your SA appliances to the desired version, when its necessary to upgrade one or more appliances to something other than the latest release of Security Analytics, or when your SA Repository has automatically synchronized and downloaded newer versions when an older version is instead needed.  It can also be used to manually synchronize the upgrade files to the SA Repository when the sync has previously failed, is timing out or simply takes too long.  
ResolutionTo manually delete the current SA repository, upload the appropriate upgrade files then recreate the repository, use these steps:  
  • Disable repository synchronization in the SA WebUI
    • In the SA WebUI, Navigate to Administration > System > Settings and uncheck the "Enable" box there.  
  • Delete all files in the following folders:
    • rm -rf /var/netwitness/srv/www/rsa/updates/RemoteRPMs/*
    • rm -rf /var/netwitness/srv/www/rsa/updates/SAUserUploaded/*
  • Use SCP or WinSCP to move the updates zip file to the SA Server folder named /var/netwitness/srv/www/rsa/updates/
  • Unzip the update zip file into /var/netwitness/srv/www/rsa/updates/SAUserUploaded
  • Change to the /var/netwitness/srv/www/rsa/updates/ folder and create the repo:
    • cd /var/netwitness/srv/www/rsa/updates/
    • createrepo .  (Note there is a space character between createrepo" and the “.” in this example.) 
  • Confirm the repo has been created by viewing the available update files: 
    • yum clean all
    • yum check-update
  • Verify the update files in the SA WebUI.