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 of the new features up to this release.

Table 1. New and Changed Information

Cisco APIC Release Version

Feature

Description

Release 4.2(1i)

Callhome email modified for clarity.

The default behavior for the Callhome email received by a user is modified for clarity.

Release 2.2(2x)

This feature was introduced

--

About Callhome

Callhome 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 automatically page a network support engineer, email a Network Operations Center, or email the Cisco Technical Assistance Center (TAC).

  • The Callhome feature can deliver alert messages containing information about diagnostics and environmental faults and events.

  • The Callhome feature can deliver alerts to multiple recipients, referred to as Callhome 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.


    Note

    Starting with Cisco APIC Release 4.2(1), the default behavior of the Callhome email received by a user has been modified for clarity. The enhanced default message provides a snippet of the exact content related to the actual fault, event, audit log, or session log that triggers the Callhome alert. However, if a user wants the verbose Callhome email that was received prior to Cisco APIC Release 4.2(1), they can configure the query group to receive the verbose output. For example, they can choose to receive queries such as <topSystem>, <eqptCh>, and <firmwareCtrlRunning> by configuring the query group. In addition, whether the user receives a default Callhome email or a verbose Callhome email, the Subject of the Callhome message contains information that is relevant to the user such as the name of the appliance, the ID number of the appliance where the fault or event is raised, and the description of the fault or event that is raised.

With the Query Group, you can include a variety of system data to the Callhome notification. When an event triggers the sending of a report, the queries in the Query Group are executed and their results are included in the report. The syntax of the queries you configured in the Query Group is the same as the API query you perform against your APICs or switches such as class query, distinguished name (DN) query with the following filters:

  • query-target—self, children, or subtree

  • rsp-subtree—no, children, or full

  • rsp-subtree-include—required, no-scoped, and so on.

See the Cisco APIC REST API Configuration Guide for details of these options.


Note
Be cognizant of what you query because some filters such as query-target=subtree, rsp-subtree=full may result in a huge number of objects that cannot be handled in one query. Such a query fails just as it does with a regular API query.

When you configure Callhome to send messages, Cisco ACI fabric system delivers Callhome 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.

  • 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 at http://www.cisco.com/. The XML format enables communication with the Cisco Systems Technical Assistance Center.

  • Archie Markup Language (ArchieML or AML)

Trigger Schedulers

Creating a Scheduler Policy Using the GUI

Procedure

Step 1

On the menu bar, choose Admin > Schedulers.

Step 2

Right-click Fabric and choose Create Trigger Scheduler.

Step 3

In the Create Trigger Schedule wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. Expand Schedule Windows by clicking the + icon.

Step 4

Create a One Time schedule.

  1. In the Window Type field, click the One Time radio button.

  2. Enter a name in the Window Name field.

  3. In the Date field, click the Calendar icon and choose the date and time.

  4. Use the up and down arrows in the Maximum Concurrent Nodes field to choose a value.

  5. Enter unlimited or a formatted value in the Maximum Running Time field.

  6. Click OK.

Step 5

Create a Recurring schedule.

  1. Expand Schedule Windows by clicking the + icon.

  2. In the Window Type field, click the Recurring radio button.

  3. Enter a name in the Window Name field.

  4. In the Day field drop-down list, choose the frequency.

  5. Use the up and down arrows in the Hour field to choose a value.

  6. Use the up and down arrows in the Minute field to choose a value.

  7. Use the up and down arrows in the Maximum Concurrent Nodes field to choose a value.

  8. Enter unlimited or a formatted value in the Maximum Running Time field.

  9. Click OK.

Step 6

Click Submit.

Attaching a Scheduler Using the CLI

Before you begin

The scheduler must be created.

SUMMARY STEPS

  1. configure terminal
  2. callhome common
  3. periodic notification schedule scheduler

DETAILED STEPS

  Command or Action Purpose

Step 1

configure terminal

Example:

switch# configure terminal

Enters configuration mode.

Step 2

callhome common

Example:

switch(config)# callhome common

Enters Callhome common policy configuration mode.

Note

 

The default name is "common" and the only name that can be created.

Step 3

periodic notification schedule scheduler

Example:

switch(config-callhome)# periodic notification schedule CallhomeScheduler

Attaches the scheduler to Callhome common.

Creating a Scheduler Policy Using the REST API

Procedure

Create a Scheduler Policy for the Callhome Feature.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/schedp-fab-callhome-sched.json

{
  "trigSchedP": {
    "attributes": {
      "descr": "Task  -­ Create a SCHEDULER Policy for Call Home Feature",
      "name": "fab-­callhome-­ sched"
    },
    "children": [
      {
        "trigAbsWindowP": {
          "attributes": {
            "name": "fab-­onetime",
            "date": "2015-­01-­ 09T21:15:55.000Z",
            "concurCap": "10"
          },
          "children": []
        }
      },
      {
        "trigRecurrWindowP": {
          "attributes": {
            "name": "fab-­ recurring",
            "hour": "1",
            "concurCap": "10"
          },
          "children": []
        }
      }
    ]
  }
}

response: {"imdata":[]}

Callhome Destination Group

Creating a Callhome Destination Group Using the GUI

Callhome data can be collected and exported to a destination group for logging and evaluation. The Create Callhome Destination Group screen contains properties for specifying a Callhome destination group.

The Callhome Destination Group is used by the Cisco ACI Fabric for sending Callhome messages.

Procedure

Step 1

Choose Admin > External Data Collectors.

Step 2

In the Navigation pane, right-click Monitoring Destinations and choose Create Callhome Destination Group.

Step 3

In the Create Callhome Destination Group wizard, perform the following actions:

  1. 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. 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 Destinations dialog box, click the + icon.

Step 5

In the Create Destinations wizard, perform the following actions:

  1. Enter a name in the Name field.

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

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

    Note

     

    Each APIC fault or event has a severity associated with it and is mapped to a Callhome urgency level. If a Callhome destination group's level is not configured properly, Callhome emails can be missed. Set the level to the appropriate option to ensure that APIC faults/events are received accordingly.

    Important: The corresponding Callhome Source configuration must also have the correct level selected.

    The mapping from the Callhome urgency level to the APIC severity is shown in the following table:

    Callhome Urgency

    APIC Severity

    Emergency

    Critical

    Alert

    Critical

    Critical

    Critical

    Error

    Major

    Warning

    Minor

    Notification

    Warning

    Information

    Info, Cleared

  4. Enter an email address in the Email field.

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

  6. Using the Maximum Size (Bytes) up and down arrows, choose a value.

  7. Click UPDATE.

Step 6

Click FINISH.

Creating a Callhome Destination Group Using the CLI

SUMMARY STEPS

  1. configure terminal
  2. callhome common
  3. destination-profile
  4. Enter destination information.

DETAILED STEPS

  Command or Action Purpose

Step 1

configure terminal

Example:

switch# configure terminal

Enters configuration mode.

Step 2

callhome common

Example:

switch(config)# callhome common

Enters Callhome common policy configuration mode.

Note

 

The default name is "common" and the only name that can be created.

Step 3

destination-profile

Example:

switch(config-callhome)# destination-profile

Configures destination profile parameters.

Creates the destination group named "common".

Step 4

Enter destination information.

Example:

switch(config-callhome-destnprof)# description "This is a test"
switch(config-callhome-destnprof)# email-contact johndoe@cisco.com
switch(config-callhome-destnprof)# phone-contact 408-526-0000

The following are the valid entries:

  • contract-id—Service contract ID of the customer.

  • customer-id—The customer ID.

  • description—The description of callhome destination-profile.

  • destination—Configure destination parameters.

    Note

     

    Multiple destinations can be created.

  • email-contact—The contact email address.

  • phone-contact—The contact phone number.

  • site-id—ID of the network where the site is deployed.

  • street-address—Street address of the site.

  • transport—Configure transport email parameters.

  • bash—Bash shell for UNIX commands.

  • export-config—Export configuration.

  • fabric—Show fabric related information.

  • import-config—Import configuration.

  • show—Show running system information.

  • terminal—Enable or disable pager for command output.

  • try—Show deployment related changes.

  • usage—Show deployment usage.

  • where—Show the current mode.

Creating a Callhome Destination Group Using the REST API

Procedure

Create a Callhome Monitoring Destination Group.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/chgroup-fab-callhome-destGrp.json

{
  "callhomeGroup": {
    "attributes": {
      "name": "fab-­callhome-­destGrp",
      "descr": "ACI Bootcamp Lab for CALLHOME"
    },
    "children": [
      {
        "callhomeDest": {
          "attributes": {
            "name": "ACI-­P1-­ Server",
            "urgency": "info",
            "email": "aci-­bc-­p1@cisco.com"
          },
          "children": []
        }
      },
      {
        "callhomeDest": {
          "attributes": {
            "name": "ACI-­P3-­ Server",
            "urgency": "info",
            "email": "aci-­bc-­p3@cisco.com",
            "format": "short-­txt"
          },
          "children": []
        }
      },
      {
        "callhomeDest": {
          "attributes": {
            "name": "ACI-­P5-­ Server",
            "urgency": "info",
            "email": "aci-­bc-­p5@cisco.com",
            "format": "aml"
          },
          "children": []
        }
      },
      {
        "callhomeProf": {
          "attributes": {
            "from": "aci-­p1-­ server@aci.bootcamp.local",
            "replyTo": "aci-­bc-­p1@cisco.com",
            "email": "aci-­bc-­ p1@cisco.com",
            "phone": "+1-­919-­392-­1234",
            "contact": "Robert Hurst",
            "addr": "123 ACI Bootcamp, Cisco",
            "contract": "1234567890",
            "customer": "12345",
            "site": "67890"
          },
          "children": [
            {
              "callhomeSmtpServer": {
                "attributes": {
                  "host": "192.169.1.161"
                },
                "children": [
                  {
                    "file RsARemoteHostToEpg": {
                      "attributes": {
                        "tDn": "uni/tn-­mgmt/mgmtp-­default/oob-­ default"
                      },
                      "children": []
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

Callhome Query Group

Creating a Callhome Query Group Using the GUI

A Callhome query group is a set of Callhome query messages to be sent on returned objects. The Callhome Query Groups panel provides the options to create or delete a Callhome query group and displays a summary table that lists the existing query groups.

The Callhome Query Group is used by the Cisco ACI Fabric for sending Callhome messages.

Procedure

Step 1

Choose Admin > External Data Collectors.

Step 2

In the Navigation pane, right-click Callhome Query Groups and choose Create Callhome Query Group.

Step 3

In the Create Callhome Query Group dialog box, perform the following actions:

  1. Enter a name in the Name field.

  2. Click the Add Queries + icon to open the Create Query wizard.

Step 4

In the Create Query wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. Click the Type of your choice.

  3. Enter DN or Class Name.

  4. Click the Target of your choice.

  5. Click the Response Subtree of your choice.

  6. Check the appropriate Response Subtree Include check boxes.

  7. Click OK.

Step 5

In the Create Callhome Query Group dialog box, click Submit.

Creating a Callhome Query Group Using the REST API

Procedure

Create a Callhome query group.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/chquerygroup-fab-queryGroup.json

{
  "callhomeQueryGroup": {
    "attributes": {
      "name": "fab-­queryGroup"
    },
    "children": [
      {
        "callhomeQuery": {
          "attributes": {
            "name": "fab-­query-­ 1",
            "target": "subtree",
            "rspSubtree": "full",
            "rspSubtreeInclude": "event-­ logs,count,stats,state,port-­deployment,tasks,relations-­with-­parent,health,add-­mo-­ list,fault-­count,local-­prefix,config-­only,record-­subtree,no-­scoped,relations,health-­ records,audit-­logs,deployment,required,faults,fault-­records"
          },
          "children": []
        }
      }
    ]
  }
}

Callhome Inventory Policy

Creating a Callhome Inventory Policy Using the GUI

The Callhome inventory policy is used to send Callhome messages with system inventory information in relation to your designated Cisco ACI fabric.

Procedure

Step 1

On the menu bar, choose Fabric > Fabric Policies.

Step 2

In the Navigation pane, expand Switch Policies.

Step 3

Right-click Policies and choose Create Callhome Inventory Policy.

Step 4

In the Create Callhome Inventory Policy wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. Click the Start Now of your choice.

  3. Using the Maximum Group Count up and down arrows, set the Maximum Retry Count.

  4. From the Destination Group drop-down list, choose the Destination Group.

  5. From the Scheduler drop-down list, choose the scheduler. .

  6. Click Submit.

Creating a Callhome Policy Using the CLI

SUMMARY STEPS

  1. configure terminal
  2. callhome common
  3. logging option
  4. logging severity severity_option

DETAILED STEPS

  Command or Action Purpose

Step 1

configure terminal

Example:

switch# configure terminal

Enters configuration mode.

Step 2

callhome common

Example:

switch(config)# callhome common

Enters Callhome common policy configuration mode.

Note

 

The default name is "common" and the only name that can be created.

Step 3

logging option

Example:

switch(config-callhome)# logging audit
switch(config-callhome)# logging event

Configures policy parameters.

Choose one of the following options:

  • audit—Enable audit and session logs to the policy.

  • event—Enable event logs to the policy.

  • fault—Enable fault logs to the policy.

  • severity—Configure minimum severity level for logs generated.

Step 4

logging severity severity_option

Example:

switch(config-callhome)# logging severity warning

These are the valid options for severity:

  • alert—Alert

  • critical—Critical

  • debug—Debug

  • emergency—Emergency

  • error—Error

  • info—Info

  • notice—Notice

  • warning—Warning

Creating a Switch Policy for Callhome Inventory Policy Using the REST API

Procedure

Create a Switch Policy for Callhome Inventory Policy.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/chinvp-­fab-­callhome-­inventory.json

{
  "callhomeInvP": {
    "attributes": {
      "name": "fab-­callhome-­inventory"
    },
    "children": [
      {
        "callhomeRsDestGroupRel": {
          "attributes": {
            "tDn": "uni/fabric/chgroup-­fab-­callhome-­ destGrp"
          },
          "children": []
        }
      },
      {
        "callhomeRsInvScheduler": {
          "attributes": {
            "tnTr igSchedPName": "fab-­callhome-­sched"
          },
          "children": []
        }
      }
    ]
  }
}

Spine Switch Policy Group

Creating a Spine Switch Policy Group Using the GUI

Procedure

Step 1

On the menu bar, choose Fabric > Fabric Policies.

Step 2

Expand Switch Policies.

Step 3

Right-click Policy Groups and choose Create Spine Switch Policy Group.

Step 4

In the Create Spine Switch Policy Group wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. From the Description drop-down list, choose the Description.

  3. From the Monitoring Policy drop-down list, choose the Monitoring Policy.

  4. From the TechSupport Export Policy drop-down list, choose the TechSupport Export Policy.

  5. From the Core Export Policy drop-down list, choose the Core Export Policy.

  6. From the Inventory Policy drop-down list, choose the Inventory Policy.

  7. From the Power Redundancy Policy drop-down list, choose the Power Redundancy Policy.

  8. From the Node Control Policy drop-down list, choose the Node Control Policy.

  9. Click Submit.

Creating a Spine Switch Policy Group Using the REST API

Procedure

Create a spine switch policy group.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/funcprof/spnodepgrp-­fab-­spine-­
policyGroup.json

{
  "fabricSpNodePGrp": {
    "attributes": {
      "name": "fab-­spine-­policyGroup",
      "descr": "ACI Bootcamp Lab Task 1.2.1 CREATE SPINE SWITCH POLICY GROUP"
    },
    "children": [
      {
        "fabricRsCallhomeInvPol": {
          "attributes": {
            "tnC allhomeInvPName": "fab-­callhome-­inventory"
          },
          "children": []
        }
      }
    ]
  }
}

Leaf Switch Policy Group

Creating a Leaf Switch Policy Group Using the GUI

Procedure

Step 1

On the menu bar, choose Fabric > Fabric Policies.

Step 2

Expand Switch Policies.

Step 3

Right-click Policy Groups and choose Create Leaf Switch Policy Group.

Step 4

In the Create Leaf Switch Policy Group wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. Enter a description in the Description field.

  3. From the Monitoring Policy drop-down list, choose the Monitoring Policy.

  4. From the TechSupport Export Policy drop-down list, choose the TechSupport Export Policy.

  5. From the Core Export Policy drop-down list, choose the Core Export Policy.

  6. From the Inventory Policy drop-down list, choose the Inventory Policy.

  7. From the Power Redundancy Policy drop-down list, choose the Power Redundancy Policy.

  8. From the Node Control Policy drop-down list, choose the Node Control Policy.

  9. Click SUBMIT.

Creating a Leaf Switch Policy Group Using the REST API

Procedure

Create a leaf switch policy group.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/funcprof/lenodepgrp-­fab-­leaf-­
policyGroup.json

{
  "fabricLeNodePGrp": {
    "attributes": {
      "name": "fab-­leaf-­policyGroup",
      "descr": "ACI Bootcamp Lab Task 1.2.2 CREATE LEAF SWITCH POLICY GROUP"
    },
    "children": [
      {
        "fabricRsCallhomeInvPol": {
          "attributes": {
            "tnC allhomeInvPName": "fab-­callhome-­inventory"
          },
          "children": []
        }
      }
    ]
  }
}

Spine Switch Profiles

Creating Spine Switch Profiles Using the GUI

Procedure

Step 1

Choose Fabric > Fabric Policies.

Step 2

In the Navigation pane, expand Switch Policies.

Step 3

Right-click Profiles and choose Create Spine Switch Profile.

Step 4

In the Create Spine Switch Profile dialog box, perform the following actions:

  1. Enter a name in the Name field.

  2. Click the Switch Associations + sign.

  3. Enter a name in the Switch Associations's Name field.

  4. From the Blocks drop-down list, choose the blocks of switches.

  5. From the Policy Group drop-down list, choose a policy group.

  6. Click UPDATE.

Step 5

Click SUBMIT.

Creating Spine Switch Profiles Using the REST API

Procedure

Create a spine switch profile.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/spprof-­fab-­spine-­swProfile.json

{
  "fabricSpineP": {
    "attributes": {
      "name": "fab-­ spine-­swProfile",
      "descr": "ACI Bootcamp Lab Task 1.3.1 CREATE SPINE SWITCH POLICY PROFILE"
    },
    "children": [
      {
        "fabricSpineS": {
          "attributes": {
            "type": "range",
            "name": "fab-­spines-­swassoc"
          },
          "children": [
            {
              "fabricNodeBlk": {
                "attributes": {
                  "from_": "201",
                  "to_": "202",
                  "name": "b44c4439ea8ad834"
                },
                "children": []
              }
            },
            {
              "fabricRsSpNodePGrp": {
                "attributes": {
                  "tDn": "uni/fabric/funcprof/spnodepgrp-­fab-­spine-­ policyGroup"
                },
                "children": []
              }
            }
          ]
        }
      }
    ]
  }
}

Leaf Switch Profiles

Creating Leaf Switch Profiles Using the GUI

Procedure

Step 1

Choose Fabric > Fabric Policies.

Step 2

In the Navigation pane, expand Switch Policies.

Step 3

Right-click Profiles and choose Create Leaf Switch Profile.

Step 4

In the Create Leaf Switch Profile wizard, perform the following actions:

  1. Enter a name in the Name field.

  2. Click the Switch Associations + icon.

  3. Enter a value in the Name field.

  4. From the Blocks drop-down-list, check the ID check boxes.

  5. From the Policy Group drop-down list, choose the Policy Group.

  6. Click Update.

Step 5

Click SUBMIT.

Creating Leaf Switch Profiles Using the REST API

Procedure

Create leaf switch profiles.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/leprof-­fab-­leaf-­swProfile.json

{
  "fabricLeafP": {
    "attributes": {
      "name": "fab-­leaf-­ swProfile",
      "descr": "ACI Bootcamp Lab Task 1.3.2 CREATE LEAF SWITCH POLICY PROFILE"
    },
    "children": [
      {
        "fabricLeafS": {
          "attributes": {
            "type": "range",
            "name": "fab-­leafs-­swassoc"
          },
          "children": [
            {
              "fabricNodeBlk": {
                "attributes": {
                  "from_": "101",
                  "to_": "104",
                  "name": "cd0b1ab33dcce538"
                },
                "children": []
              }
            },
            {
              "fabricRsLeNodePGrp": {
                "attributes": {
                  "tDn": "uni/fabric/funcprof/lenodepgrp-­fab-­leaf-­ policyGroup"
                },
                "children": []
              }
            }
          ]
        }
      }
    ]
  }
}

Callhome Source

Creating a Callhome Source Using the GUI

Fabric policies govern the operation of internal fabric interfaces. The system provides default fabric policies. Fabric policies enable configuring various functions or protocols. Administrators who have fabric administrator privileges can create new fabric policies according to their requirements. The APIC enables administrators to select the pods, leaf switches, and interfaces to which they will apply access policies.

Fabric policies configure interfaces that connect spine and leaf switches. Fabric policies can enable features such as monitoring (statistics collection and statistics export), troubleshooting (on-­demand diagnostics and SPAN), or NTP.

The call home source profile, which determines the information to deliver and the urgency level for sending email-­based alert notifications to a call home destination. A range of message formats are available for compatibility with pager services or XML-­ based automated parsing applications. You can use this feature to automatically page a network support engineer, email a Network Operations Center, or email the Cisco Technical Assistance Center (TAC).

Fabric Callhome Sources need to be configured in the DEFAULT and COMMON monitoring policies configured in the Fabric Policies configuration. Use the GUI to configure the DEFAULT and COMMON Callhome monitoring policies. Use the API Inspector to capture the API POST information from this configuration.

Procedure

Step 1

Choose Fabric > Fabric Policies.

Step 2

In the Navigation pane, expand Policies, Monitoring, and default.

Step 3

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

Step 4

In the Callhome/Smart Callhome/SNMP/Syslog/TACACS work pane, choose the Callhome option from the Source Type.

Step 5

Click + to open the Create Callhome Source dialog box.

Step 6

In the Create Callhome Source dialog box, perform the following actions:

  1. Enter a name in the Name field.

  2. Check the appropriate Include check boxes.

  3. From the Level drop-down list, choose a Callhome urgency level.

    Note

     

    Each APIC fault or event has a severity associated with it and is mapped to a Callhome urgency level. If a Callhome source's level is not configured properly, Callhome emails may not be sent. Set the level to the appropriate option to ensure that APIC faults/events are captured and emailed accordingly.

    Important: A Callhome Destination Group assigned to this source must also have the correct level selected.

    The mapping from the Callhome urgency level to the APIC severity is shown in the following table:

    Callhome Urgency

    APIC Severity

    Emergency

    Critical

    Alert

    Critical

    Critical

    Critical

    Error

    Major

    Warning

    Minor

    Notification

    Warning

    Information

    Info, Cleared

  4. From the Destination Group drop-down list, chose a destination group.

  5. From the Query Group drop-down list, choose a query group.

  6. Click Submit.

Creating a Callhome Source Using the REST API

Procedure

Create the Callhome source.

Example:

POST https://192.168.1.141/api/node/mo/uni/fabric/monfab-­default/chsrc-­fab-­callhome-­
source.json

{
  "callhomeSrc": {
    "attributes": {
      "name": "fab-­callhome-­ source",
      "incl": "events,audit,faults",
      "urgency": "info"
    },
    "children": [
      {
        "callhomeRsDestGroup": {
          "attributes": {
            "tDn": "uni/f abric/chgroup-­fab-­callhome-­ destGrp"
          },
          "children": []
        }
      },
      {
        "callhomeRsQueryGroupRel": {
          "attributes": {
            "t Dn": "uni/fabric/chquerygroup-­fab-­queryGroup"
          },
          "children": []
        }
      }
    ]
  }
}