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 HTTPS

Updated: June 12, 2026

Want to summarize with AI?

Log in

Configures Call Home to use HTTPS as the transport method by establishing destination profiles, setting secure URLs, and defining alert group subscriptions, while ensuring proper certificate trustpoint configuration for secure data transmission.

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

Note

For the HTTPS function to work you should use the crypto ca trustpoint command to declare a CA, followed by the crl option command. This ensures that the certificates of other peers are accepted without trying to obtain the appropriate CRL. For example:

RP/0/RP0/CPU0:ios(config)#crypto ca trustpoint Trustpool
RP/0/RP0/CPU0:ios(config-trustp)#crl optional

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 http

Example:

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

Configures the message transport method for HTTPS.

5.

destination address http url

Example:

Router(config-call-home-profile) # destination address http https://example.com

Configures the destination URL 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

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 ("").