New and Changed Information

The following table provides an overview of the significant changes up to this current release. The table does not provide an exhaustive list of all changes or the new features up to this release.

New and Changed Information

Cisco APIC Release Version

Feature

Description

Release 3.2(1)

This feature was introduced

--

- About Smart Callhome

About Smart Callhome

Smart Callhome provides an email-based notification for critical system policies in a similar way as Callhome. However, Smart Callhome collects a more specific selection of faults to deliver in email messages.

Note

Smart Callhome only collects and delivers faults.

The fault triggers that are typical of the Smart Callhome feature correspond to the kind of events that threaten to disrupt your network. Examples are:

- Temperature Faults: The temperature of a sensor exceeds a threshold.

- Fan/ Power Supply Faults: A fan or power supply unit goes offline.

- Disk Utilization Faults: The disk usage of a device exceeds a threshold.

Smart Callhome collects faults and emails them to a network support engineer, a Network Operations Center, or to the Cisco Technical Assistance Center (TAC).

Creating a Smart Callhome Destination Group and Destinations Using the GUI

Smart Callhome faults can be collected and exported to a destination group for delivery to your network support team or Cisco's Smart Callhome services. The Create Smart Callhome Destination Group screen contains properties for specifying a Smart Callhome destination group and associated destinations.

The Smart Callhome Destination Group is used by the Cisco ACI Fabric for sending Smart Callhome messages to configured destinations.

Procedure

Step 1

Choose Admin > External Data Collectors.

Step 2

In the Navigation pane, right-click Monitoring Destinations and choose Create Smart Callhome Destination Group. Alternatively, expand Monitoring Destinations in the Navigation pane, click Smart Callhome, and in the Smart Callhome work pane, click theActions drop down list, then clickCreate Smart Callhome Destination Group.

Step 3

In the Create Smart Callhome Destination Group dialog, perform the following actions:

1. (Required) Enter a name in the Name field.

2. Enter a description in the Description field.

3. From the Admin State drop-down list, choose a value.

4. Use the Port Number up and down arrows to choose the port number.

5. (Required) Enter the IP address of the SMTP server in the SMTP Server field.

6. From the Management EPG drop-down list, choose a value.

7. Enter an email address in the From Email field.

8. Enter an email address in the Reply To Email field.

9. Enter an email address in the Customer Contact Email field.

10. Enter a phone number in the Phone Contact field.

11. Enter a name in the Contact Information field.

12. Enter an address in the Street Address field.

13. Enter a contact id value in the Contract Id field.

14. Enter the customer ID in the Customer Id field.

15. Enter the site ID in the Site Id field.

16. Click Next.

Step 4

In the Smart Destinations dialog box, click the + symbol above the Create Smart Destinations table.

Step 5

In the Create Smart Destinations table editor, perform the following actions:

1. Enter a name in the Name field.

2. From the Admin State drop-down list, choose a value.

3. Enter an email address in the Email field.

4. From the Format drop-down list, choose a format.

5. Put a check in the RFC Compliant box if you want the emails to be in an RFC-compliant format.

If you put a check in the box, then, among other things, the email includes the description of the fault in the email body, which makes the email human-readable. If you do not put a check in the box, the email instead includes the description of the fault in the subject.

6. Click Update.

Step 6

Click Finish.

Creating a Smart Callhome Destination Group Using the NX-OS-Style CLI

Smart Callhome collects faults and emails them to a network support engineer, a Network Operations Center, or to the Cisco Technical Assistance Center (TAC).

You can use the NX-OS-style CLI to configure Smart Callhome destination groups and destinations. A Smart Callhome destination group enables you to create a list of email destinations to which fault data is sent. You can create one or more destinations in a group. After the destination group is created, you can associate it with a Smart Callhome source, either for the entire switch fabric supported by the Cisco Application Policy Infrastructure Controller (Cisco APIC) or for a specific Tenant.

The following example CLI commands show how to configure a Smart Callhome destination group and destination using the NX-OS-style CLI:

Procedure

Step 1

Enter the configuration mode.

Example:

apic1# config

Step 2

Enter the Smart Callhome common policy configuration mode.

Example:

apic1(config)# smartcallhome common

Note

The default name for the common policy configuration mode is "common". It is the only name that can be created.

Step 3

Create a Smart Callhome destination group.

Example:

In the following command, a Smart Callhome destination group is created:

apic1(config-smartcallhome)# destination-profile

Step 4

Configure an SMTP server in the new destination group.

Example:

In the following command, an SMTP server with an IP address of "10.10.10.2" is added to the destination group:

apic1(config-callhome-destnprof)# transport email mail-server 10.10.10.2

Step 5

Configure profile parameters about the new Smart Callhome destination group.

Example:

The following commands provide additional information about the destination group:

- contract-id: The service contract ID of the customer.

- customer-id: The customer ID.

- description: A description for the Smart Callhome destination profile.

- email-contact: The customer contact e-mail address.

- phone-contact: The customer contact phone number.

- site-id: The ID of the site where the network is deployed.

- street-address: The street address of the site.

Step 6

Create a Smart Callhome destination in the new destination group.

Example:

In the following command, a remote Smart Callhome destination named "sch-dest-1" is created:

apic1(config-callhome-destnprof)# destination sch-dest-1

Step 7

Configure specific parameters for the new remote Smart Callhome destination.

Example:

In the following command example, the following characteristics are configured for the new remote destination:

- Email address: net-admin@site.com

- Message format: Short text

- RFC Compliant: True

apic1(config-callhome-destnprof-destn)# email-addr net-admin@site.com
apic1(config-callhome-destnprof-destn)# format short-txt
apic1(config-callhome-destnprof-destn)# rfc-compliant true

The result of this configuration is the creation of a Smart Callhome destination group containing a remote email destination. If you want the same Smart Callhome fault data sent to multiple email destinations, you can repeat steps 5 and 6 as many times as needed.

Creating a Smart Callhome Destination Group Using the REST API

Procedure

Create a Smart Callhome destination group.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric.json

{
"callhomeSmartGroup": {
"attributes": {
"name": "<destination-group-name>",
"descr": "<description>"
},
"children": [
{
"callhomeSmartDest": {
"attributes": {
"name": "<destination-name>",
"email": "<email-address>",
format="xml"
},
"children": []
}
},

{
"callhomeProf": {
"attributes": {
"from": "<email-address>",
"port": "<number>",
"replyTo": "<email-address>",
"email": "<customer-contact-email>",
"phone": "<contact-phone-number>",
"contact": "<name>",
"addr": "<streeet-address>",
"contract": "<id>",
"customer": "<id>",¬
"site": "<id>"
},
"children": [
{
"callhomeSmtpServer": {
"attributes": {
"host": "<hostname-or-ip-address>"
},
"children": [
{
"file RsARemoteHostToEpg": {
"attributes": {
"tDn": "uni/tn-mgmt/mgmtp-default/oob- default"
},
"children": []
}
}
]
}
}
]
}
}
]
}
}

Creating a Smart Callhome Source Using the GUI

The Smart Callhome source is used by the Cisco ACI Fabric to collect fault information to send in messages to destinations created in Smart Callhome destination groups.
The origin of the faults collected is dependent on where the source is configured. If, for example, the Smart Callhome source is created for the Fabric, then all faults generated in all switches supported by the Cisco APIC are collected and delivered to the associated Smart Callhome destinations. Alternatively, the source can be configured for a specific tenant or for external access policies. Subsequently, faults associated with the tenant or external access policy are collected and delivered to the associated destinations.

Note

You can only create one Smart Callhome source for a specific monitoring policy (fabric policy, external access policy, or tenant).

The following procedure configures a Smart Callhome source in the fabric policy.

Procedure

Step 1

Choose Fabric > Fabric Policies.

Step 2

In the Navigation pane, expand the following:

1. Policies

2. Monitoring

3. Common Policy

Step 3

Click Callhome/Smart Callhome/SNMP/Syslog/TACACS.

Step 4

In the Callhome/Smart Callhome/SNMP/Syslog/TACACS work pane, click the Smart Callhome tab.

Step 5

In the Smart Callhome work pane, double-click the Faults entry (under Include).

If the Faults entry does not exist, follow these steps:

1. Click the Actions drop-down list, then click Create Smart Callhome Source. Alternatively, right-click Callhome/Smart Callhome/SNMP/Syslog/TACACS in the Navigation pane and select Create Smart Callhome Source.

2. In the Create Smart Callhome Source dialog, choose a destination group from the Destination Group drop-down list.

Note

If you do not want to choose an existing Smart Callhome destination group in the drop-down list, or one is not available, create one by clicking Create Smart Callhome Destination Group.

3. Click Submit.

Step 6

In the Smart Callhome Source dialog, choose a destination group from the Destination Group drop-down list.

Note

If you do not want to choose an existing Smart Callhome destination group in the drop-down list, or one is not available, create one by clicking Create Smart Callhome Destination Group.

Step 7

Click Submit.

Trademarks

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS REFERENCED IN THIS DOCUMENTATION ARE SUBJECT TO CHANGE WITHOUT NOTICE. EXCEPT AS MAY OTHERWISE BE AGREED BY CISCO IN WRITING, ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS DOCUMENTATION ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.

The Cisco End User License Agreement and any supplemental license terms govern your use of any Cisco software, including this product documentation, and are located at: http://www.cisco.com/go/softwareterms.Cisco product warranty information is available at http://www.cisco.com/go/warranty. US Federal Communications Commission Notices are found here http://www.cisco.com/c/en/us/products/us-fcc-notice.html.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any products and features described herein as in development or available at a future date remain in varying stages of development and will be offered on a when-and if-available basis. Any such product or feature roadmaps are subject to change at the sole discretion of Cisco and Cisco will have no liability for delay in the delivery or failure to deliver any products or feature roadmap items that may be set forth in this document.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)