System Management Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

System Management Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Sending Call-home Data through an Email

Updated: June 12, 2026

Want to summarize with AI?

Log in

Configures Call Home to use email as the transport method by defining destination profiles, specifying recipient email addresses, selecting message formats, and subscribing to relevant alert groups for automated event reporting.

This task enables the user to configure sending Call-home data using email as the transport method:

Procedure

1.

call-home

Example:

Router(config) # call-home

Enters Call Home configuration mode.

2.

profile name

Example:

Router(config-call-home) # profile user1

Enters call home destination profile configuration mode for the specified destination profile name. If the specified destination profile does not exist, it is created.
3.

active

Example:

Router(config-call-home-profile) # active

Enables the destination profile. By default, a user-defined profile is enabled when it is created.
4.

destination transport-method email

Example:

Router(config-call-home-profile) # destination transport-method email

Configures the message transport method for email. This is the default
5.

destination address email email-address

Example:

Router(config-call-home-profile) # destination address email xyz@cisco.com

Configures the destination e-mail address to which Call Home messages are sent.
6.

destination preferred-msg-format {long-text |short-text| xml}

Example:

Router(config-call-home-profile) # destinationpreferred-msg-format xml

(Optional) Configures a preferred message format. The default is XML.

7.

subscribe-to-alert-group syslog severity severity-level pattern string

Example:

Router(config-call-home-profile) # subscribe-to-alert-group syslog severity normal pattern COUNT
Router(config-call-home-profile) # commit

Configures a destination profile to receive messages for the syslog alert group. Alerts with a severity the same or greater than the specified severity level are sent.

  • critical—Includes events requiring immediate attention (system log level 1).

  • disaster—Includes events with significant network impact.

  • fatal—Includes events where the system is unusable (system log level 0).

  • major—Includes events classified as major conditions (system log level 2).

  • minor—Includes events classified as minor conditions (system log level 3).

  • normal—Specifies the normal state and includes events classified as informational (system log level 6).

    This is the default.

  • notification—Includes events informational message events (system log level 5).

  • warning—Includes events classified as warning conditions (system log level 4).

You can specify a pattern to be matched in the syslog message. If the pattern contains spaces, you must enclose it in quotes ("").