This document provides the steps to take when troubleshooting an issue
with the Smart Call Home (SCH) feature after it has already been
Cisco recommends that you have knowledge of these topics:
This document is not restricted to specific software and hardware
Technical Tips Conventions for more information on document
Here is a short video on configuring:
Home Configuration on UCS
Assuming that you have already checked the configuration and have
registered for the SCH service, complete these steps in order to troubleshoot
SCH issues in the UCS B-series servers.
SSH to the UCS active FI.
debug callhome all
In a web browser connect to the UCSM.
In the Navigation pane, click the Admin tab.
On the Admin tab, expand All > Communication Management >
In the Work pane, click the System Inventory tab.
In the Actions area, click Send System Inventory
In the FI under nxos prompt: undebug all Check to see if an email was
sent out to the recipient configured for Call Home. If you did not and you see
errors in your debug output check your SCH configuration on the UCS. Otherwise,
continue to the next step.
Try to capture the SCH mail packets with ethanalyzer. Ethanalyzer
provides sniffing capabilities to NX-OS within the operating system,
simplifying the need for a third party network probe.
In nxos under nxos prompt:
debug callhome all
ethanalyzer local sniff-interface mgmt capture-filter "port smtp"
By default Ethanalyzer captures up to 10 frames. Utilize the
limit-captured-frames to change the value or set it to a
different value or remove the limit by using the value 0.
This is an attempt to collect the debug and packet capture for the
same event, and to limit the packet capture to only the smtp
Repeat step 4 to send the inventory again. Follow this with step 5 to
turn off the debug and ethanalyzer. Note: CTRL+C can be utilized to stop the
Again, check to see if an email was sent out to the recipient
configured for Call Home. If your configuration is correct you should see the
email go out in the ethanalyzer capture. If the recipients did not get the
email check ethanlyzer output for Simple Mail Transfer
Protocol (SMTP) errors. It can be that the SMTP server is not
If the emails were sent out to the recipient configured for Call
Home, but a SCH Cisco TAC Service Request (SR) was not opened
go to this page: tools.cisco.com/sch
This link will allow you to find out if the SCH backend has received
any call-home alerts.
They have all sorts of reports that you can run based on serial
number/hostname device-id, etc.
If you want to run test a Call Home alert instead of sending the
inventory you can try the following in the place of the System
The following is an excerpt from this page:
a Test Call Home Alert
Step 1 UCS-A# scope monitoring
Enters monitoring mode.
Step 3 UCS-A /monitoring/callhome # send-test-alert
Sends a test Call Home alert using one or more of the following alert parameters:
Event severity level
When a test Call Home alert is sent, Call Home responds as it would to
any other alert and delivers it to the configured destination email addresses.
The next example sends a test Call Home alert to the configured
destination email address of the environmental alert group:
UCS-A# scope monitoring
UCS-A /monitoring # scope callhome
UCS-A /monitoring/callhome # send-test-alert alert-description
"This is a test alert" alert-group environmental
Aside from the simple configuration problems, issues with networking
or the mail servers are seen. Also, registration issues are common.
The IP address of the fabric inter-connects and the virtual IP address
might need to be set up as a relay on the SMTP server.
Creating a new user registration requires:
Valid Cisco.com ID for the to-be registered person.
At least one valid contract for the company that is supported by
Smart Call Home, when the to-be registered person needs to be registered as an
A short video on
Configure and Register Your Devices
With registration issues go to this link in order to resolve the issue
as this involves the SCH registration team:
Smart Call Home