Smart Call Home
Smart Call Home is an automated support capability that helps to minimize downtime by performing proactive diagnostics in Cisco UCS Central. Cisco UCS Central sends system generated real-time alerts to the email address specified in your Call Home settings. You can view details on any detected issues on the Cisco Smart Call Home support page, along with recommendations for possible remediation.
For more information, see the Smart Call Home Web Application chapter of the Smart Call Home User Guide.
Smart Call Home provides alerts for the Cisco UCS Central faults listed in Smart Call Home Faults.
If you want to receive alerts for Cisco UCS Manager faults, see Configuring Call Home for UCS Manager.
Configuring Smart Call Home Using the CLI
Use this procedure to configure and enable Smart Call Home.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC # connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC (policy-mgr) # scope org |
Enters organization mode. |
Step 3 |
UCSC (policy-mgr) /org # scope device-profile |
Enters device profile mode. |
Step 4 |
UCSC (policy-mgr) /org/device-profile # scope smart-callhome |
Enters Smart Call Home mode. |
Step 5 |
UCSC (policy-mgr) /org/device-profile/smart-callhome # enable |
Enables Smart Call Home. |
Example
This example shows how to enable and configure Smart Call Home.
UCSC # connect policy-manager
UCSC (policy-mgr) # scope org
UCSC (policy-mgr) /org # scope device-profile
UCSC (policy-mgr) /org/device-profile # scope smart-callhome
UCSC(policy-mgr) /org/device-profile/smart-callhome # set contract-id
UCSC(policy-mgr) /org/device-profile/smart-callhome/ # set customer-id
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # set email
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # set phone-contact
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # set site-id
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # set street-address
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # set throttling
UCSC(policy-mgr) /org/device-profile/smart-callhome/* # enable
Configuring an HTTP Proxy Using the CLI
Use this procedure to configure an HTTP proxy for Smart Call Home.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC(policy-mgr)# scope org |
Enters organization root mode. |
Step 3 |
UCSC(policy-mgr)# /org scope device-profile |
Enters device-profile mode. |
Step 4 |
UCSC(policy-mgr) /org/device-profile # scope smart-callhome |
Enters the default Smart Call Home policy configuration mode. |
Step 5 |
UCSC(policy-mgr) /org/device-profile/smart-callhome # scope proxy |
Scopes the Transport Gateway. |
Step 6 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/proxy # set {port | url} |
Sets the proxy parameters. |
Step 7 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/proxy # commit-buffer |
Example
This example shows how to configure an HTTP proxy for Smart Call Home.
UCSC # connect policy-manager
UCSC(policy-mgr) # scope org
UCSC(policy-mgr) /org # scope device-profile
UCSC(policy-mgr) /org/device-profile # scope smart-callhome
UCSC(policy-mgr) /org/device-profile/smart-callhome/ # scope proxy
UCSC(policy-mgr) /org/device-profile/smart-callhome/proxy # set port 80
UCSC(policy-mgr) /org/device-profile/smart-callhome/proxy # set url 10.0.0.1
UCSC(policy-mgr) /org/device-profile/smart-callhome/proxy # commit-buffer
Configuring System Inventory for Smart Call Home Using the CLI
Use this procedure to configure inventory options for Smart Call Home.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC # connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC (policy-mgr) # scope org |
Enters organization mode. |
Step 3 |
UCSC (policy-mgr) /org # scope device-profile |
Enters device profile mode. |
Step 4 |
UCSC (policy-mgr) /org/device-profile # scope smart-callhome |
Enters Smart Call Home mode. |
Step 5 |
UCSC (policy-mgr) /org/device-profile/smart-callhome # scope inventory |
Enters inventory mode. |
Step 6 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set interval-days interval-days |
Sets the system inventory interval days (1-30). |
Step 7 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set send-periodically {on | off } |
Sets the frequency for sending inventory. |
Step 8 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set timeofday-hour timeofday-hour |
Sets the inventory hour of the day to send (1-23). |
Step 9 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set timeofday-minute timeofday-minute |
Sets the inventory minute of the hour to send (0-59). |
Step 10 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # commit-buffer |
Commits the transaction to the system configuration. |
Example
This example shows how to scope and configure inventory options:
UCSC # connect policy-manager
UCSC(policy-mgr)# scope org
UCSC(policy-mgr) /org # scope device-profile
UCSC(policy-mgr) /org/device-profile # scope smart-callhome
UCSC(policy-mgr) /org/device-profile/smart-callhome # scope inventory
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory # set interval-days 30
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set send-periodically on
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set timeofday-hour 23
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # set timeofday-minute 59
UCSC(policy-mgr) /org/device-profile/smart-callhome/inventory* # commit-buffer
Configuring the Transport Gateway Using the CLI
Use this procedure to configure the transport gateway to communicate with the Cisco Smart Call Home portal. The transport gateway acts as a proxy between Cisco UCS Central and the Smart Call Home servers at Cisco.com.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC(policy-mgr)# scope org |
Enters organization root mode. |
Step 3 |
UCSC(policy-mgr) /org # scope device-profile |
Enters device-profile mode. |
Step 4 |
UCSC(policy-mgr) /org/device-profile # scope smart-callhome |
Scopes the default Call Home policy's configuration mode. |
Step 5 |
UCSC(policy-mgr) /org/device-profile/smart-callhome # scope transport-gateway |
Scopes the Transport Gateway. |
Step 6 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set url URL of transport gateway |
Sets the HTTP address for the transport gateway URL. |
Step 7 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set certificate transport gateway certificate |
Sets the gateway certificate if you are using a secure (HTTPS) URL for access. |
Step 8 |
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set enabled {yes | no} |
Enables the transport gateway. |
Example
The following example shows how to enable and configure the transport gateway:
UCSC # connect policy-manager
UCSC(policy-mgr) # scope org
UCSC(policy-mgr) /org # scope device-profile
UCSC(policy-mgr) /org/device-profile # scope smart-callhome
UCSC(policy-mgr) /org/device-profile/smart-callhome # score transport-gateway
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set URL 10.0.0.1
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set certificate
Transport Gateway Certificate:
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # set enabled yes
UCSC(policy-mgr) /org/device-profile/smart-callhome/transport-gateway # commit-buffer
Viewing the Destination Profile Using the CLI
Follow these steps to view the CiscoTAC-1 default destination profile.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC(policy-mgr)# scope org |
Enters organization root mode. |
Step 3 |
UCSC(policy-mgr)# /orgscope device-profile |
Enters organization root mode. |
Step 4 |
UCSC(policy-mgr) /org/device-profile # scope smart-callhome |
Scopes the default Smart Call Home policy configuration mode. |
Step 5 |
UCSC (policy-mgr) /org/device-profile/smart-callhome # show profile detail |
|
Configuring Smart Call Home Alerts Using the CLI
Use this procedure to set Smart Call Home alerts.
Procedure
Command or Action | Purpose | |
---|---|---|
Step 1 |
UCSC# connect policy-mgr |
Enters policy manager mode. |
Step 2 |
UCSC(policy-mgr)# scope org |
Enters organization root mode. |
Step 3 |
UCSC(policy-mgr)# /orgscope device-profile |
Enters device-profile mode. |
Step 4 |
UCSC(policy-mgr) /org/device-profile # scope smart-callhome |
Scopes the default Call Home policy's configuration mode. |
Step 5 |
UCSC(policy-mgr) /org/device-profile/smart-callhome # create alerts {capacity-exceeded | client-lost-connectivity | controller-lost-connectivity | core-file-generated | db-connect-read-write-error | duplicated-assigned | invalid-keyring-certificate | invalid-trustpoint-cert-chain | not-in-compliance | provider-lost-connectivity | remote-failed} |
Creates an alert. |
Step 6 |
UCSC(policy-mgr) /org/device-profile/callhome/profile* # set admin-state {enable | disable} |
Sets the admin-state. |
Step 7 |
UCSC(policy-mgr) /org/device-profile/callhome/profile/destination* # commit-buffer |
Commits the transaction to the system configuration. |
Example
The following example shows how to create and enable an alert:
UCSC # connect policy-manager
UCSC(policy-mgr) # scope org
UCSC(policy-mgr) /org # scope device-profile
UCSC(policy-mgr) /org/device-profile # scope smart-callhome
UCSC(policy-mgr) /org/device-profile/callhome # create alerts client-lost-connectivity
UCSC(policy-mgr) /org/device-profile/callhome/profile/alerts* # set admin-state disabled
UCSC(policy-mgr) /org/device-profile/callhome/profile/alerts* # commit-buffer
Smart Call Home Registration
When you first enable Cisco UCS Central Smart Call Home, Cisco UCS Central automatically sends the system inventory to the Cisco Smart Call Home servers. It sends an automated email message to the email address, that you entered, with a link to the Smart Call Home portal. You have 3 months (90 days) to confirm the registration.
After you register, if you did not enter a contract ID, a 4 month (120 days) trial period activates. If you entered a valid contract ID, your registration is complete. Make sure that you enter the contract ID and send the inventory before the 120 days trial period to re-activate your registration.
Smart Call Home Faults
The faults described in this section cause the fabric interconnect to raise Smart Call Home alerts. For more information on Cisco UCS Central faults, see the appropriate Cisco UCS Central Faults Reference.
Fault Name |
Fault Code |
Explanation |
---|---|---|
fltSysdebugCoreCoreFile |
F10000005 |
Fault occurs when one of the processes stops responding. Cisco UCS Central generates a core file. |
fltExtpolProviderProviderLostConnectivity |
F10000190 |
Provider is not reachable from the Cisco UCS Central registry. This fault typically occurs if the provider process has stopped responding, or is too busy to respond to a heartbeat message sent by the registry. |
fltExtpolControllerControllerLostConnectivity |
F10000191 |
Controller is not reachable from the Cisco UCS Central registry. This fault typically occurs if the controller process has stopped responding, or is too busy to respond to a heartbeat message sent by the registry. |
fltExtpolClientClientLostConnectivity |
F10000192 |
Registered UCS domain is not reachable from the Cisco UCS Central registry. This fault typically occurs if the UCS domain has lost network access or UCS domain DME process has stopped responding, or is too busy to respond to a heartbeat message sent by registry. |
fltIdentpoolElementDuplicatedAssigned |
F10000208 |
Two or more service profiles possess the same ID. This fault occurs when Cisco UCS Central finds one ID is assigned to two or more service profiles probably from local pools. |
fltConfigDbConfigStats-DB-Error |
F10000536 |
Fault occurs when the statistics database is configured incorrectly or if the database is down or out of disk space. |
fltPkiTPStatus |
F10000591 |
Fault occurs when the TrustPoint certificate status has become invalid. |
ltPkiKeyRingStatus |
F10000592 |
Fault occurs when the Keyring certificate status has become invalid. |
fltConfigBackupUngrouped-domain |
F10000616 |
Remote scheduled backup failed. This fault typically occurs if the admin supplied the wrong password, host, user name, or path to the remote machine. |
fltStorageItemCapacityExceeded |
F10000034 |
Fault occurs when the partition disk usage exceeds 70% but is less than 90%. |
fltStorageItemCapacityWarning |
F10000035 |
Fault occurs when the partition disk usage exceeds 90%. |
fltSmartlicenseEntitlementEnforcementModeFault |
F10000750 |
Entitlement for a license is not compliant. |