Nutanix Life Cycle Management voor Dell XC


Life Cycle Manager allows you to view all software and firmware updates from a single pane of glass. From the LCM dashboard you can do an inventory for all the entities in the cluster.

LCM support new features for the Dell XC platforms in version 1.2.

LCM is supported for the Dell 13G hardware family on AHV and on ESXi 5.5 and 6.0.
This release adds LCM inventory and update support for the following components:
• BIOS
• iDRAC
• HBA controller
• NIC
• Data drives (SSD and HDD)

All the Dell XC  updates are packaged within a Payload. A payload level determines what firmware versions are supported for LCM update. You can see on a fresh updated LCM on a Dell XC cluster the following dashboard:


The Prism UI does not provide visiblility into the payload. Check this PDF for the current payloads for LCM 1.2. https://s3.amazonaws.com/ntnx-portal/documentation/kb/lcm-dell-payloads-v1.2.pdf

You can see multiple software the LCM has inventoried. I explain some of the software you can expect:
• iSM is the needed module to allow PT Agent to talk to the iDRAC in the hypervisor (ESXi in this customer's case)
• PT Agent is the service that does the inventory and updates under the hood of LCM for Dell systems.
• Firmware payload is the collection of component binaries and system descriptions that make up the various XC appliances.

LCM 1.2 has dependencies that will resolve themselves if you do the updates. iSM and PT Agent are required to make our payload work properly with LCM.

The picture below lets see the packages within the Dell Update Manager and Hardware entities:


In the next article I describe how you can update the packages for the first time.
See: https://softwaredriven.blogspot.nl/2017/10/update-nutanix-lcm.html

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