Showing results for 
Search instead for 
Do you mean 
POST AN IDEA
0 Kudos

OS Deployment

Status: Not able to implement
by OfirGan on ‎06-13-2017 01:22 AM

Hi

 

as for Today, if the xClarity is not sync with the server and you start OS deployment, it fail because the xClarity send the wrong power action to the server.

 

why is it depend on the server power state?!? or maybe its a bug...

 

Not sync = the server is ON but xClarity server didn't acknowledge it yet, it still show that the server is OFF

Status: Not able to implement

XClarity Administrator feature OS deploy requires booting to an iso for the bootstrap process.  This requires the host to be rebooted so an accurate power state must be known.  If there are discrepancies in the power state creating a failure, that would be bug.  You can sure post to the XClarity Community to determine if others have seen or call into service for further assistance.

 

If your idea has been misunderstood, please comment as such with further information to be looked at again.  Thank you for participating in the ideation program!

0 Kudos

Recovery_ID for I/O module

Status: Acknowledged
by OfirGan on ‎06-07-2017 10:50 AM

since 8.4.3 f for CN4093 and similar switches, its not possible to access the switch if it has connection issue to xClarity server.

 

Its possible to access to the CMM/IMM using the Recovery_ID user.

 

Why isn't it possible to use this user to access the switch in case of a connection issue to the xClarity? 

 

Status: Acknowledged

Thank you for the clarification.  We will move this forward in process with the planning team.

0 Kudos

Boot server to Bios from any current state

Status: Acknowledged
by OfirGan on ‎06-07-2017 10:22 AM

From the IMM its possible to boot the server from any state (ON/Off) to BIOS,

but from xClarity its only possible to restart the server to BIOS only if it acknowledge that the server is ON.

 

If the server is OFF you need to turn it on, than wait for xClarity to refresh the server state and only than you can boot the server to BIOS.

 

Status: Acknowledged

Thank you for providing an idea on how to improve XClarity.  This will be reviewed with the product management team over the next couple weeks to assess if they are interested in putting this in the backlog of features.

0 Kudos

We have three different NTP servers in our environment. For high availability reasons it would be great to configure at least two NTP servers in Lenovo XClarity. As far as I know, it is only possible to enter one NTP server at the moment (v 1.3.0).

Status: Acknowledged

Thank you for the idea.  This will be reviewed with the offering team as next step then will move to "Considering Implementation" or "Not able to implement".

0 Kudos

Customer requirement request.  Provide for the ability to import a pool of IMM FOD keys; also request for an Enterprise level IMM FOD key that covers a certain number of endpoints.  Once the keys are imported or downloaded, XClarity Administrator should be able to distribute this key or set of keys to the desired system IMM's.  Would also like the ability to easily deactivate a key on one system, so that it could be used on a different system if the user deems that the advanced function is no longer needed/desired on a system (floating pool was how it was explained)

Status: Acknowledged
0 Kudos

Request from customer.  Add the ability to centrally manage user accounts for the IMM/CMM and push updates to endpoints.  This would include the ability to push new passwords to these devices for those clients that are on a schedule in which they must change passwords.  That includes the ability to update the password for the RECOVERY_ID account created when using centralized management.  This would be very beneficial in sceanrios where the endpoint is configured with the "Secure" security policy in which password expiration is enforced.

Status: Acknowledged
0 Kudos

Add the ability to use standard LDAP servers for authentication within XClarity Administrator.  Today, the only external LDAP solution supported is Microsoft Active Directory.  This requirement came from a customer.

Status: Considering Implementation

The planning team has reviewed and requested this move forward in process for consideration in a future release.  It will be tracked as LXCA-2714 in our backlog for prioritization. 

 

Title/Description: : Add the ability to use standard LDAP servers for authentication within XClarity Administrator.

 

Acceptance Criteria:I should be able to configure XClarity Administrator to one or more LDAP instances. If there are more than one configured, we will assume they are replicas of each other and user authentication should take no more than 5-10 seconds under normal condition.

When XClarity Administrator is configured correctly, all XClarity Administrator function will work correctly.

 

If the information provided is incorrect or incomplete, feel free to provide additional comments.  At the point this idea is implemented, it will be moved to "Implemented" and the release provided will be updated.

 

Thank you for participation and idea!

0 Kudos

Currently LXCA is issuing certificates to managed endpoints with self signed root CA, it would be nice to have option to act as subordinate of the signed root CA

Status: Considering Implementation

The planning team has reviewed and requested this move forward in process for consideration in a future release.  It will be tracked as LXCA-2716 in our backlog for prioritization. 

 

Title: As an Administrator, I want to continue to use my existing certificate authority for XClarity Administrator to manage endpoints to reduce the number of certificate authorities in my environment

 

Description: Currently LXCA is issuing certificates to managed endpoints with self signed root CA.  It would be nice to have option to act as subordinate of the signed root CA.

 

Acceptance Criteria:   No special criteria identified.

 

If the information provided is incorrect or incomplete, feel free to provide additional comments.  At the point this idea is implemented, it will be moved to "Implemented" and the release provided will be updated.

 

Thank you for participation and idea!

0 Kudos

Moto themes

Status: Not able to implement
by Kiranronaldo on ‎05-16-2017 12:08 AM

Why don't you add themes for Moto phones it will admire customers like mi phones

 

Status: Not able to implement

This idea does not apply to the XClarity product set.

0 Kudos

Provide Update History for Endpoints

Status: Acknowledged
by Lenovo Employee BigJay on ‎05-05-2017 08:41 AM

Add a view within XClarity Administrator that allows the admin to view the history of firmware applied to a system (all components) along with the current firmware applied within that same view.  Of course this information should be able to be exported.  All supported APIs and scripting tools (REST, PowerShell etc..)  should also be able to extract this information.

Status: Acknowledged
0 Kudos

Recently, I tried to add xclarity integrator to our test vcenter that is running vcenter 6.0 behind a vmware platform service controller.  We have a total of 4 vcenters, all behind the same platform service controller for our vdi environment per design from vmware.  so here is the issue:

 

for testing, i only wanted to have my test environment see the xclarity integrator in the web client.  i was not tryng to add the integrator to all my other vcenters at this time. Howeve, it appears that the web client for vcenter is trying to apply the lxci to all my vcenters

 

here is my question to the powers that be

since vmware is heading the way of allowing multiple vcenters to be under 1 psc, is there a way to lxca to manage all vcenters in a psc or web client?  forgive me for the poor wording of the question....  

 

please reach out if you have any further questions

0 Kudos

XClarity Administrator:

Allow for creation of a Policy that can be assigned to a Flex chassis bay/bays that results in automatic firmware update provisioning, assign server profile, and install Operating system as soon as a compute node is inserted into a Flex chassis bay.

Status: Considering Implementation

The planning team has reviewed and requested this move forward in process for consideration in a future release.  It will be tracked as LXCA-1761 in our backlog for prioritization. 

 

Title:  As a customer, I want all new nodes inserted inot a Flex Chassis to brought to a specific firmware and OS level to reduce the time required to manage new nodes.

 

Description: Allow for creation of a Policy that can be assigned to a Flex chassis bay/bays that results in automatic firmware update provisioning, assign server profile, and install Operating system as soon as a compute node is inserted into a Flex chassis bay.

 

Acceptance Criteria:   This should demonstrate the creation of the policy to be used for new systems. Once the node is added to XClarity Administrator, the node should be brought to the right levels of firmware and os as specified in the policy without error. Any error path must have clear recoverable messages for the customer with recommendations on how to correct for a retry of the operation.

 

If the information provided is incorrect or incomplete, feel free to provide additional comments.  At the point this idea is implemented, it will be moved to "Implemented" and the release provided will be updated.

 

Thank you for participation and idea!

Top tags