Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Pulse IOT agent upgrade procedure from 2.0.0 to 2.0.1 (76368)

Last Updated: 1/7/2020Categories: InformationalTotal Views: 2982Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This document contains the step by step procedure for upgrading pulse IOT agent. This will be used by the customers/partners to upgrade the VMware Pulse IOT Center agents from 2.0.0 to 2.0.1

Solution

Follow the below steps to upgrade VMware Pulse IOT Center agents from 2.0.0 to 2.0.1:

Agent Upgrade Procedure:

After upgrading the on-premise version of VMware Pulse IoT Center from 2.0.0 to 2.0.1, apply the following patch on all the upgraded instances:

Prerequisites:

SSH and SCP or WINSCP utility on the local system or VM to log in and copy the VMware Pulse IoTC Agent packages to the Pulse Server Nodes.

SSH access to all the 3 Pulse Server Nodes for root user.

Download the patch for VMware Pulse IoTC Agent binaries (all the tar.gz and the manifest.json files) to local system or VM from where you apply the patch.

Steps to Download:

Log in to https://customerconnect.vmware.com/group/vmware/patch.

Select Product: Pulse IoT Center, Version: 2.0.1 and click Search.

Select the patch with name Pulse-IoTc-2.0.1-14869950.tar.gz and Click Download.

Download the Load Balancer CA cert:

Log in to the VMware Pulse Administrator console of the Load Balancer.

Navigate to the Certificate Management section and download the loadBalancer.crt file under Load Balancer Certificate.

Ensure that loadBalancer.crt does not include a space in the file name.

Delete the older VMware Pulse IoTC Agent packages Under Campaign Packages:

Log in to the VMware Pulse IoT Center console and navigate to Updates > Packages.

Select and delete all the Agents with version 2.0.1-14825020.

Note: These packages must not be part of any campaign.

Procedure:

Perform the following steps on all the Pulse Server Nodes:

Login to Pulse Server Node as root user.

Backup the contents of /opt/vmware/iotc/iotc-agent/artifacts/ folder:

mkdir -p /opt/vmware/iotc/iotc-agent/artifacts_back
mv /opt/vmware/iotc/iotc-agent/artifacts/* /opt/vmware/iotc/iotc-agent/artifacts_back

Log out of the Node and copy the newly downloaded VMware Pulse IoTC Agent binaries (tar.gz and the manifest.json files) to the /opt/vmware/iotc/iotc-agent/artifacts/ folder using SCP or WINSCP.

scp <Path to the Agent packages>/*.gz root@<Server Node IP>:/opt/vmware/iotc/iotc-agent/artifacts/
scp <Path to the Agent packages>/manifest.json  root@<Server Node IP>:/opt/vmware/iotc/iotc-agent/artifacts/

Log in to the Node through SSH and set the permissions to the antifactory:

chmod 755 -R /opt/vmware/iotc/iotc-agent/artifacts/*

After running the steps successfully, run the following script to create campaign packages for the VMware Pulse IoTC Agent upgrade:

sh /etc/bootstrap/postupdate.d/02-agent-upgrade.sh

Re-bundle the VMware Pulse IoTC Agents with the Load Balancer CA certificate.

Log in to the VMware Pulse Administrator console of the respective Pulse node.

Navigate to Certificate Management > Rebundle VMware Pulse IoT Center Agent. Click Replace.

Browse and select the loadBalancer.crt file. Enter the VMware Pulse IoT Center FQDN, which is the Load Balancer FQDN.

Click Next and then click Replace.

Repeat Step 1 through Step 7 for the other Pulse Server Nodes.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
NSX-T ユーザー インターフェースのトランスポート ノード ステータスに「不明」と表示される (76382)

KB
•
vCenter Server の統合、クロス ドメイン再ポイント、および新規デプロイ中に「install.vmafd.vmdir_vdcpromo_error_21」エラーが発生する (74678)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Pulse IoT Center 2.x

Take Our Survey

Support Assistant