Schneider Electric Product Part Number Guide

[Ermengardi Atkisson]

Electricalequipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.

The technical literature and declarations of conformity can be accessed on the Schneider Electric Exchange website, ecobuilding.schneider-electric.com. Contact your local Schneider Electric sales office for hard copy of documentation or for additional information.

action_zoom_plus_stroke WARNING: This product can expose you to chemicals including lead which is known to the State of California to cause cancer and which is known to the State of California to cause birth defects or other reproductive harm. For more information go to www.P65Warnings.ca.gov

When procuring rolling stock, which includes train control, communication, traction power equipment, and rolling stock prototypes, the cost of the components and subcomponents produced in the U.S. must be:

Final assembly for rolling stock also must occur in the U.S. Additionally, rolling stock procurements are subject to the pre-award and post-delivery Buy America audit provisions set forth in 49 U.S.C. 5323(m) and 49 CFR part 663.

Unlike rolling stock, manufactured goods must be 100-percent produced in the U.S. A manufactured good is considered produced in the United States if: (1) All of the manufacturing processes for the product take place in the United States; and (2) All of the components of the product are of U.S. origin. A component is considered of U.S. origin if it is manufactured in the United States, regardless of the origin of its subcomponents. 49 CFR 661.5(d). FTA has issued a number of Buy America guidance letters discussing manufactured goods.

This product guide provides essential presales information to understand the Lenovo XClarity Orchestrator offering and its key features, specifications, and compatibility. This guide is intended for technical specialists, sales specialists, sales engineers, IT architects, and other IT professionals who want to learn more about LXCO and consider its use in IT solutions.

Lenovo XClarity Orchestrator (LXCO) provides centralized monitoring, management, provisioning, and analytics for environments with large numbers of devices. It leverages existing resource managers (such as Lenovo XClarity Administrator, Lenovo XClarity Management Hub and Schneider Electric EcoStruxure IT Expert) across multiple sites to view overall health, collect device inventory and health summaries, drill down into device details, view event and audit logs, and apply updates to managed resources.

With the latest support for ThinkEdge Client Devices being managed via the XClarity Management Hub, this enables you to manage Lenovo ThinkSystem, ThinkAgile, ThinkEdge Servers and ThinkEdge client devices all from the one Lenovo XClarity Orchestrator (LXCO) interface for a complete data center-to-edge management solution.

You can use XClarity Orchestrator to maintain current software levels on managed resources. You can use the updates catalog to know what software levels are available, use update-compliance policies to identify which resources need to be updated based on custom criteria, and then deploy the desired updates to those resources. LXCO ensures that software is provisioned on the target resources in the correct order.

You can quickly provision managed servers using a consistent configuration. Configuration settings (such baseboard management controller and UEFI settings) are saved as a pattern that can be applied to multiple servers.

XClarity Orchestrator does not directly deploy configuration patterns to managed servers. Instead, it sends a request to the applicable resource manager to start a job to perform the deployment, and then tracks the progress of the request.

You can use XClarity Orchestrator to deploy operating-system images to multiple servers. XClarity Orchestrator does not directly deploy operating system to managed servers. Instead, it sends a request to the applicable XClarity Administrator resource manager to start a job to perform the update, and then tracks the progress of the request.

XClarity Orchestrator can be set up to collect and send diagnostic files automatically to Lenovo Support using Call Home when certain serviceable events occur in managed resources. You can also manually collect diagnostic files, open a problem record, and send diagnostic files to the Lenovo Support Center.

The Dashboard is the hub of Lenovo XClarity Orchestrator that provides access to information that is important to you. It contains report cards that each summarize the status of resources and activities in your environment, including devices health, vulnerabilities, compliance, and alerts.

It is important that you evaluate the security requirements in your environment, understand all security risks, and minimize those risks. Lenovo XClarity Orchestrator includes several features that can help you secure your environment.

Lenovo XClarity Orchestrator provides a set of tools that you can use to collect and send service files to Lenovo Support, set up automatic notification to service providers when certain serviceable events occur on specific devices, view service-ticket status, and warranty information. You can contact Lenovo Support to get help and technical assistance when you run into problems.

As a requirement you must set up at least one (and up to four) Network Time Protocol (NTP) server to synchronize the timestamps for Lenovo XClarity Orchestrator with events that are received from resource managers.

Note: The XClarity Orchestrator virtual appliance and its host must be set to synchronize to the same time source to prevent inadvertent time mis-synchronization between XClarity Orchestrator and its host.

You can use Lenovo XClarity Orchestrator for the following provisioning options for your managed resources, such as deploying updates to Lenovo XClarity Administrator resource managers and managed servers, configuring managed servers and deploying Operating Systems.

You can use Lenovo XClarity Orchestrator to maintain current software levels on Lenovo XClarity Administrator resource managers and managed servers. You can use the updates catalog to know what software levels are available, use update-compliance policies to identify which resources need to be updated based on custom criteria, and then deploy the desired updates to those resources.

Server-configuration patterns are used to quickly configure multiple servers from a single set of defined configuration settings. Each pattern defines the configuration characteristics for a specific type of server. You can create a server pattern by learning the settings from an existing server.

Lenovo XClarity Orchestrator generates analytics alerts based on known hardware and firmware issues, monitors trends to detect anomalies that occur in your managed resources and builds heuristics that can calculate the likelihood of impending problems or failures. The trends are visualized as queries, graphs, and charts that show the compliance status, problem history, and breakdown of resources that have the most problems. You can then analyze these trends to get insights into the cause of problems and resolve them quickly.

To use the analytics functions, a Lenovo XClarity Orchestrator Analytics license is needed for each device that supports the analytics functions. See the Download and ordering information section for ordering information.

Lenovo XClarity Orchestrator is a for-fee application and thus requires a Software entitlement license to be purchased. When managing XClarity Administrator resource Managers this is additional to the XClarity Pro Licensing which is required for the resource managers (i.e. XClarity Administrator). You can use XClarity Orchestrator for free for up to 90 days using the free-trial license; however, after the free trial expires, you must purchase and install Lenovo XClarity Orchestrator Standard licenses for all managed devices to continue using XClarity Orchestrator.

License compliance is determined based on the number of devices that are managed by XClarity Orchestrator. The number of managed devices must not exceed the total number of licenses in all active license keys. If XClarity Orchestrator is not in compliance with the installed licenses (for example, if licenses expire or if managing additional devices exceeds the total number of active licenses), you have a grace period of 90 days to install appropriate licenses.

Lenovo XClarity Orchestrator, Lenovo XClarity Orchestrator Edge Client Devices and Lenovo XClarity Orchestrator Analytics software entitlements licenses are available as 1-year, 3-year, or 5-year software subscription and support.

Lenovo XClarity Orchestrator and Lenovo XClarity Orchestrator Analytics licenses are available on a per-managed-endpoint basis or per-managed-chassis basis. The per chassis licenses offer a more cost-effective way of purchasing licenses for the Flex System environment. Lenovo XClarity Orchestrator Edge Client Devices Licenses are available on a per-managed-client basis.

When you purchase XClarity Orchestrator, the order is fulfilled via electronic software delivery (ESD) using the Lenovo Key Management System (LKMS). The order is placed onto LKMS using an email address for the end user who has ordered the code. This email address is where the Activation Code is sent in PDF format (the email will come from lkm...@lenovo.com). The recipient email address is the login to the LKMS system for administration and to manage the LKMS inventory.

The Activation code is redeemed via LKMS and the information about the end customer should be entered during the redemption process. The customer information is then used to send the electronic proof of entitlement (will come from sw_ov...@lenovo.com ) and a welcome letter along with an explanation of how to obtain the code from the LKMS Site: .

You can find a complete list of supported ThinkEdge Client devices and options (such as I/O, DIMMs, and storage adapters), minimum required firmware levels, and limitations considerations from the following page:

3a8082e126