How to Enable and Disable the Call Home Feature

Call Home in UCS Overview

Call Home provides an email-based notification for critical system policies. A range of message formats are available for compatibility with pager services or XML-based automated parsing applications. You can use this feature to page a network support engineer, email a Network Operations Center, or use Cisco Smart Call Home services to generate a case with the Technical Assistance Center.

The Call Home feature can deliver alert messages containing information about diagnostics and environmental faults and events.

The Call Home feature can deliver alerts to multiple recipients, referred to as Call Home destination profiles. Each profile includes configurable message formats and content categories. A predefined destination profile is provided for sending alerts to the Cisco TAC, but you also can define your own destination profiles.

When you configure Call Home to send messages, Cisco UCS Manager executes the appropriate CLI show command and attaches the command output to the message.

Cisco UCS delivers Call Home messages in the following formats:

Short text format which provides a one or two line description of the fault that is suitable for pagers or printed reports.
Full text format which provides fully formatted message with detailed information that is suitable for human reading.
XML machine-readable format that uses Extensible Markup Language (XML) and Adaptive Messaging Language (AML) XML Schema Definition (XSD). The AML XSD is published on the Cisco.com website. The XML format enables communication with the Cisco Systems Technical Assistance Center.

For information about the faults that can trigger Call Home email alerts, see the Cisco UCS Faults and Error Messages Reference.

The following figure shows the flow of events after a Cisco UCS fault is triggered in a system with Call Home configured:

Flowchart showing events that can occur after a fault is triggered in a Cisco UCS domain — Figure 1. Flow of Events after a Fault is Triggered

Enabling Call Home

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope monitoring	Enters monitoring mode.
Step 2	UCS-A /monitoring # scope callhome	Enters monitoring call home mode.
Step 3	UCS-A /monitoring/callhome # enable	Enables Call Home.
Step 4	UCS-A /monitoring/callhome # commit-buffer	Commits the transaction to the system configuration.

Example

The following example enables Call Home and commits the transaction:

UCS-A# scope monitoring
UCS-A /monitoring # scope callhome
UCS-A /monitoring/callhome # enable
UCS-A /monitoring/callhome* # commit-buffer
UCS-A /monitoring/callhome #

What to do next

For more information on the Call Home feature, see the Cisco UCS System Monitoring Guide.

Disabling Call Home

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope monitoring	Enters monitoring mode.
Step 2	UCS-A /monitoring # scope callhome	Enters monitoring call home mode.
Step 3	UCS-A /monitoring/callhome # disable	Enables Call Home.
Step 4	UCS-A /monitoring/callhome # commit-buffer	Commits the transaction to the system configuration.

Example

The following example disables Call Home and commits the transaction:

UCS-A# scope monitoring
UCS-A /monitoring # scope callhome
UCS-A /monitoring/callhome # disable
UCS-A /monitoring/callhome* # commit-buffer
UCS-A /monitoring/callhome #

What to do next

For more information on the Call Home feature, see the Cisco UCS System Monitoring Guide.

Cisco UCS Manager Administration Management Using the CLI, Release 3.1 (3)

Bias-Free Language

Book Title

Cisco UCS Manager Administration Management Using the CLI, Release 3.1 (3)

Chapter Title