Configuration Management - Backup Restore, Firmware Deploy
      Back to home
      1. Support Portal
      2. Features
      3. Configuration Management - Backup Restore, Firmware Deploy

      Debug Fileserver/Backup/Firmware/Deploy

      This article describes how to enable debug logging when issues with backup/restore/deploy cannot be resolved through normal troubleshooting procedures.

      If you are getting errors with backups/restore/deploy here are some troubleshooting steps to assist.

      External Fileserver Required for Production  

      Most issues reported with backup/restore/deploy are because the default  windows internal fileserver is being used in production. This internal file server is  designed for QA and Testing.  It is highly recommended that customer to setup and use and external file server. (filezilla is one example)

      NOTE: the Linux OVA Appliance comes with a built in file server native to the Linux OS. This is considered to be an external file server and may be used for production deployments 

      1. For Windows, You must set up and external file server if you don't already  have one setup.
        1. Once set up, retry the operation to see if using the external servers has resolved the issue. You can associate your file server to the application by going to Configuration management -> File Servers portlet.
        2. Go to step 2 if still having issues.  
      2. Verify the image from deployment is staged on the the FTP/SFTP.
        1. Open the shared drive on your fileserver to see if the files are showing up while you try the backup, restore or deploy operation again.  

      The back up restore or deploy process simply send a command the the target device instructing it what to do. For a backup example, the device receives a command like copy-run-ftp  with the file server IP address embedded.  the device  copies the file to the server and Cruz then pull it off the file server and save to the db.

      Problems can be investigated at these points:

      • Can Cruz logon  the device to issue the commands (if no,  check firewalls between the target and Cruz, check credentials associated to the device)
      • Was the file copied to the file server?  (if no, check firewalls between the target and file server.  Try manually logging into the device and issue the copy command.)
      • Was Cruz able to retrieve the file from the file server  (if no, check firewalls between the file server and Cruz
      • If the issue cannot be resolved continue:

        Enable Debugging and Provide output to Support

        Troubleshooting device deploy/backup/restore

        • Stop App/Med Server

        • cd $OWARE_USER_ROOT/owareapps/installprops/lib/installed.properties

        • vi installed.properties and add the following to the end of the file.

        • Turn on the following debug categories
        installed.properties File 
            
        ENABLE Debug
                     
                          com.dorado.mediation.cli=true
                          com.dorado.redcell.filexferapi=true
                          com.dorado.redcell.netrestore.deploy=true

         DIABLE Debug     com.dorado.mediation.cli=false
                          com.dorado.redcell.filexferapi=false
                          com.dorado.redcell.netrestore.deploy=false

        • Restart App/Med Server

        Recreate the Issue -Deploy/Backup/Restore

        Now that the debug is enable and the server is backup and running

        1. Re-Deploy on the device to generated the error and acputre the debug in the server.log filel
        2. Reverse the Enable Debug process by replacing =true to =False > Restart App/Med Server
        3. Send the server.log file to support for analysis (generated a new ticket i you already don'g have one: tsc@doradosoftware.com)

        Server.log Location

        cmd> cd $OWARE_ROOT/jboss-5.1/server/oware/log

        Windows Default Path:
        C:\Program Files\Dell EMC\OpenManage\Network Manager\oware\jboss-5.1\server\oware\log

        Linux Default Path:
        /opt/VAroot/dellemc/openmanage/networkmanager/oware/jboss-5.1/server/oware/log