You can generate and tech support files for Cisco UCS Central and registered Cisco UCS Domains. Collecting remote tech support includes the following:

• Generate Tech Support: You can generate tech support files for Cisco UCS Central or each registered UCS domains.

• Download tech support files: Download the created tech support file to view information.

  Note	You can download the tech support file only from the Cisco UCS Central GUI.

If you configure deferred deployment in a Cisco UCS domains, Cisco UCS Central enables you to view all pending activities. You can view all the activities that are waiting for user acknowledgment and those that have been scheduled.

If a Cisco UCS domain has pending activities, the Cisco UCS Central GUI notifies users with admin privileges when they log in.

Cisco UCS Central displays information about all pending activities, including the following:

• Name of the service profile to be deployed and associated with a server

• Server affected by the deployment

• Disruption caused by the deployment

• Change performed by the deployment

• Whether an activity is acknowledged.

You can also acknowledge the activities.

You cannot specify the maintenance window in which a specific pending activity is applied to the server. The maintenance window depends on the number of pending activities and on the maintenance policy assigned to the service profile. However, any user with admin privileges can manually initiate a pending activity and reboot the server immediately, whether an activity is waiting for an user acknowledgment or for a maintenance window.

To view the pending activities on Cisco UCS Central GUI, click the Alerts icon from the menu bar.

Cisco UCS Central collects and displays all the Cisco UCS Central system faults on the Fault Logs page. To view these system fault logs, click the Alerts icon and select System Faults. The Faults Logs page displays information on the type and severity level of the fault, and allow you to monitor and acknowledge the system faults, and filter the faults that are displayed.

The faults table includes the following information for each fault:

• Code—The ID associated with the fault

• Timestamp—Date and time at which the fault occurred

• Type—Origin of the fault

• Cause—Cause of the fault

• Affected Object—The component that is affected by this fault

• Fault Details—The details of the fault.

• Severity—The severity of the fault

• Action—Any action required by the fault

To manage the information that is collected, see Configuring UCS Central System Policies.

Cisco UCS Central collects and displays faults from registered Cisco UCS domains in the UCS Domain Faults Log page. The faults are displayed by type and severity level. You can click on the fault type to expand and view the exact Cisco UCS domains where the faults have occurred. The UCS domain fault logs are categorized and displayed as follows:

• Fault Level—The fault level that triggers the profile. This can be one of the following:

  • Critical—Critical problems exist with one or more components. These issues should be researched and fixed immediately.

  • Major—Serious problems exist with one or more components. These issues should be researched and fixed immediately.

  • Minor—Problems exist with one or more components that might adversely affect the system performance. These issues should be researched and fixed as soon as possible before they become major or critical issues.

  • Warning—Potential problems exist with one or more components that might adversely affect the system performance if they are allowed to continue. These issues should be researched and fixed as soon as possible before they get worse.

  • Healthy—No fault in any of the components in a domain.

  • Unknown—No fault in any of the components in a domain.

• No Of Domains—The number of domains where the faults have occurred of each severity level.

• Domain—The domain where the faults have occurred. Click a type to see the Cisco UCS domains that have one or more faults of that type and the details of the fault.

• Critical—The number of critical faults of the selected type in the Cisco UCS domain.

• Major—The number of major faults of the selected type in the Cisco UCS domain.

• Minor—The number of minor faults of the selected type in the Cisco UCS domain.

• Warning—The number of warning faults of the selected type in the Cisco UCS domain.

This table is displayed only when you select a domain from the UCS Domain Faults page.

• Filter—Allows you to filter the data in the table.

• ID— The unique identifier associated with the fault.

• Timestamp—The day and time at which the fault occurred.

• Type— Information about where the fault originated.

• Cause— A brief description of what caused the fault.

• Affected Object—The component that is affected by this issue.

• Fault Details—More information about the log message.

• Severity—Displays an icon denoting the fault severity. The icon key appears below the table.

Cisco UCS Central collects and displays the events that occurred in the system, such as when a user logs in or when the system encounters an error. When such events occur, the system records the event and displays it in the Event Logs. To view these event logs, click the Alerts icon from the menu bar, and select Events. The event logs record information on the following:

• ID—Unique identifier associated with the event that caused the fault

• Timestamp—Date and time at which the event occurred

• Trig. By—Type of user associated with the event

• Affected Object—The component that is affected by the event

You can view a comprehensive list of configuration changes in Cisco UCS Central in the Audit Logs. When you perform configuration changes involving creating, editing or deleting tasks in the Cisco UCS Central GUI or the Cisco UCS Central CLI, Cisco UCS Central generates an audit log. In addition to the information related to configuration, the audit logs record information on the following:

• Resources that were accessed.

• Date and time at which the event occurred.

• Unique identifier associated with the log message.

• The user who triggered an action to generate the audit log. This can be an internal session or an external user who made a modification using the Cisco UCS Central GUI or the Cisco UCS Central CLI.

• The source that triggered the action.

• The component that is affected.

If an error occurs that causes the system to crash, then a core dump file is created. This core dump file includes information of the state of the system before the error occurred, and the time at which the system crashed. To view the core dump files, click the Alerts icon on the menu bar and select Core Dumps. In the Core Dumps log table you can view the following information:

• Timestamp—When the core dump file was created.

• Name—The full name of the core dump file.

• Description—The type of core dump file.

You can view active sessions for remote and local users in Cisco UCS Central and choose to terminate those sessions from the server. To view the active sessions, click the Alerts icon on the menu bar and select Sessions. In the Active Sessions log table you can view the following information:

• ID—The type of terminal from which the user logged in.

• Timestamp—Date and time at which the user logged in.

• User—The user name.

• Type—The type of terminal from which the user logged in.

• Host—The IP address from which the user logged in.

• Status—Whether the session is currently active.

• Actions—Click Terminate to end the selected session.

Internal service logs provide information on various providers and the version of the Cisco UCS Central associated with the provider. To view the internal services, click the Alerts icon on the menu bar and select Sessions.

In the Services section of the Internal Services page, you can view the following information:

• Name—The type of the provider.

• Last Poll—Day and time on which Cisco UCS Central last polled the provider.

• IP Address—The IP address associated with the provider.

• Version—The version of Cisco UCS Central associated with the provider.

• Status—The operational state of the provider.

In the Clean Up section of the Internal Services page, you can view the following information:

• Domain—The domain name.

• Last Poll—Day and time on which Cisco UCS Central last polled the provider.

• Lost Visibility—When Cisco UCS Central lost visibility to the provider.

• Clean Up—Click Clean Up to remove all references of this Cisco UCS domain from Cisco UCS Central.

  Note	The domain must be re-registered with Cisco UCS Central before it can be managed again by Cisco UCS Central.