Update the LCM packages for the first time on Dell XC

Life Cycle Management has designed to take care of all the necessary Dell tools, like the ones I mentioned in an earlier post: https://softwaredriven.blogspot.nl/2017/10/life-cycle-management-12-voor-dell-xc.html

You can update components on production clusters in use. But it is recommended for the first time of running LCM 1.2, to do it during off-hours as the cluster requires a reboot per node to install iSM and PT Agent. This two components are necessary before the LCM can download the payload.

Once the payload is downloaded, you can run an inventory again so LCM can determine what components need to be updated. Depending on the size of the cluster, this can take up to 10 minutes (for 3 node cluster) or longer depending on the number of components to be found.

When you update a component, LCM put the host in maintenance mode. Then LCM put all the components in a queue to be updated. At the end of the update process, the system will do a reboot. After the reboot, the node will be returned to the cluster. This process will continues per node, until all nodes are updated.

LCM validates cluster health before allowing to update the components, so a compromised cluster will not get updated. But an inventory will always proceed.

You don’t need to worry about dependencies and actions, LCM will get the job done. The idea is that you can select one/some of all available updates and go. The firmware payload is the actual binaries containing the updates for the component being upgraded.

I will update my components soon and edit this blog item. I will come back….

Comments

Post a Comment

Popular posts from this blog

Error when opening LCM via PRISM

Image
After the upgrade to AOS 5.1.5, my LCM console gave the following message. Json Rpc request for unkown Rpc object LifeCycleManager Error message You can solve this issue by doing the following steps: 1). Verified that the PRISM shows: JSON RPC request error. 2). verified from ~$ zkls /appliance/logical/pyleaders/lcm_leader/   one of the CVM was not listed. I have 9. n_0000000096 n_0000000097 n_0000000098 n_0000000099 n_0000000100 n_0000000101 n_0000000102 n_0000000103 3). Verified One of the CVM .101 has .genesis_restart_required_path file. ~$  allssh "ls -latr ~/.genesis_restart_required_path" 4). Removed the file and restarted genesis on all the CVMs. ~$  rm .genesis_restart_required_path ~$  allssh genesis restart 5). Verified the issue does not exist anymore.
Read more

Azure AD Connect DB corrupt

Image
ADSync SQL connection problem I've got in a situation that our Azure AD Connect Synchonisation Server Manager was giving the status " stopped-database-connection-lost ". Only we did't mention this message, because every object was synced successful. After some problems with Azure Active Directory self-service password reset, I've decide to check the event logs. Event logs I found differend events errors, most of them mentioned the following error " The server encountered an error because the connection to SQL Server failed. ". When I opened Azure AD Connect tool, the configuration wizard was not giving me any errors of database problems. Event 6322, ADSync The server encountered an error because the connection to SQL Server failed. Event 6075, ADSync The management agent "domain.local" failed on run profile "Delta Import" because the connection to the server database was lost. E...
Read more

Get the Exchange 2010 DB whitespace back

Image
For exchange administrators it is sometime necessary to see how our Exchange databases are doing. You don't want that the database and transaction log on the datastores run out of disk space. Most of the time I want to see the blank space that is within a database. This blank space is sometimes called: Free space Free database pages Available Mailbox Space White space Checking White Space in Exchange 2010 Get the Whitespace from all the databases, run the following command: Get-MailboxDatabase -Status | Sort-Object availablenewmailboxspace | ft name,databasesize,availablenewmailboxspace -auto Show all softdeleted and disabled mailboxes in Exchange 2010 After you choose the DB you want to clear the whitespace, please check the softdeleted and disabled mailbox accounts per database with the following command: Get-MailboxStatistics -Database " DB1 " | Where-Object {$_.DisconnectDate -Notlike $NULL} | Format-Table DisplayName, DisconnectDate, MailboxG...
Read more