Call Home

Call Home offers proactive diagnostics and real-time alerts on select Cisco devices, which provides higher network availability and increased operational efficiency. Smart Call Home is a secure connected service of Cisco SMARTnet for the Cisco cBR routers.

Finding Feature Information

Your software release may not support all the features that are documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. The Feature Information Table at the end of this document provides information about the documented features and lists the releases in which each feature is supported.

Contents

Hardware Compatibility Matrix for the Cisco cBR Series Routers


Note
The hardware components that are introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified.
Table 1. Hardware Compatibility Matrix for the Cisco cBR Series Routers

Cisco CMTS Platform

Processor Engine

Interface Cards

Cisco cBR-8 Converged Broadband Router

Cisco IOS-XE Release 16.5.1 and Later Releases

Cisco cBR-8 Supervisor:

  • PID—CBR-SUP-250G

  • PID—CBR-CCAP-SUP-160G

  • PID—CBR-CCAP-SUP-60G

  • PID—CBR-SUP-8X10G-PIC

Cisco IOS-XE Release 16.5.1 and Later Releases

Cisco cBR-8 CCAP Line Cards:

  • PID—CBR-LC-8D30-16U30

  • PID—CBR-LC-8D31-16U30

  • PID—CBR-RF-PIC

  • PID—CBR-RF-PROT-PIC

  • PID—CBR-CCAP-LC-40G

  • PID—CBR-CCAP-LC-40G-R

Cisco cBR-8 Downstream PHY Modules:

  • PID—CBR-D30-DS-MOD

  • PID—CBR-D31-DS-MOD

Cisco cBR-8 Upstream PHY Modules:

  • PID—CBR-D30-US-MOD

  • PID—CBR-D31-US-MOD

Prerequisites for Call Home

  • Contact e-mail address (required for full registration with Smart Call Home, optional if Call Home is enabled in anonymous mode), phone number (optional), and street address information (optional) should be configured so that the receiver can determine the origin of messages received.


    Note

    Contact e-mail address is not required if you enable Smart Call Home by enabling smart licensing.

  • At least one destination profile (predefined or user-defined) must be configured. The destination profile(s) configured depends on whether the receiving entity is a pager, e-mail, or automated service such as Cisco Smart Call Home.

    • If the destination profile uses e-mail message delivery, you must specify a Simple Mail Transfer Protocol (SMTP) server.

    • Configuring the trustpool certificate authority (CA) is not required for HTTPS server connection as the trustpool feature is enabled by default.

  • The router must have IP connectivity to an e-mail server or the destination HTTP(S) server.

  • To use Cisco Smart Call Home service, an active service contract covering the device is required to provide full Smart Call Home service.


    Note

    An active service contract is only required for full Smart Call Home services like automatically raising a Cisco Technical Assistance Center (TAC) case.

Restrictions for Call Home

  • If there is no IP connectivity or if the interface in the VRF to the profile destination is down, Smart Call Home messages cannot be sent.

  • Smart Call Home operates with any SMTP server.

  • You can configure up to five SMTP servers for Smart Call Home.

Information About Call Home

The Call Home feature provides email-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard email, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, email notification to a network operations center, XML delivery to a support website, and use of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC).

The Call Home feature can deliver alert messages containing information on configuration, environmental conditions, inventory, syslog, snapshot, and crash events.

The Call Home feature can deliver alerts to multiple recipients, referred to as Call Home destination profiles , each with configurable message formats and content categories. A predefined destination profile (CiscoTAC-1) is provided, and you also can define your own destination profiles. The CiscoTAC-1 profile is used to send alerts to the backend server of the Smart Call Home service, which can be used to create service requests to Cisco TAC, the service will depend on the Smart Call Home service support in place for your device and the severity of the alert.

Flexible message delivery and format options make it easy to integrate specific support requirements.

Benefits of Call Home

  • Automatic execution and attachment of relevant CLI command output.

  • Multiple message format options such as the following:

    • Short Text—Suitable for pagers or printed reports.

    • Full Text—Fully formatted message information suitable for human reading.

    • XML—Matching readable format using Extensible Markup Language (XML). The XML format enables communication with the Cisco TAC.

  • Multiple concurrent message destinations.

  • Multiple message categories including configuration, crash, diagnostic, environment, inventory, snapshot, and syslog.

  • Filtering of messages based on severity and pattern matching.

  • Scheduling of periodic message sending.

Obtaining Smart Call Home Services

If you have a service contract directly with Cisco, you can register for the Smart Call Home service. Smart Call Home analyzes Smart Call Home messages and provides background information and recommendations. For critical issues, Automatic Service Requests are generated with the Cisco TAC.

Smart Call Home offers the following features:

  • Continuous device health monitoring and real-time alerts.

  • Analysis of Smart Call Home messages and, if needed, Automatic Service Request generation routed to the correct TAC team, including detailed diagnostic information to speed problem resolution.

  • Secure message transport directly from your device or through an HTTP proxy server or a downloadable Transport Gateway (TG). You can use a TG aggregation point to support multiple devices or in cases where security dictates that your devices may not be connected directly to the Internet.

  • Web-based access to Smart Call Home messages and recommendations, inventory, and configuration information for all Smart Call Home devices provides access to associated field notices, security advisories, and end-of-life information.

You need the following items to register for Smart Call Home:

  • SMARTnet contract number for your router.

  • Your e-mail address

  • Your Cisco.com username

For information about how to configure Call Home to work with the Smart Call Home service, see the Smart Call Home.

Anonymous Reporting

Smart Call Home is a service capability included with many Cisco service contracts and is designed to assist customers resolve problems more quickly. In addition, the information gained from crash messages helps Cisco understand equipment and issues occurring in the field. If you decide not to use Smart Call Home, you can still enable Anonymous Reporting to allow Cisco to securely receive minimal error and health information from the device. If you enable Anonymous Reporting, your customer identity will remain anonymous, and no identifying information is sent.


Note

When you enable Anonymous Reporting, you acknowledge your consent to transfer the specified data to Cisco or to vendors operating on behalf of Cisco (including countries outside the United States). Cisco maintains the privacy of all customers. For information about how Cisco treats personal information, see the Cisco Privacy Statement at Cisco Online Privacy Statement

When Call Home is configured in an anonymous way, only crash, inventory, and test messages are sent to Cisco. No identifying information is sent.

For more information about what is sent in these messages, see the Alert Group Trigger Events and Commands section.

Smart Licensing

Smart Licensing uses the Smart Call Home service.

The Smart Licensing service is an alternative licensing architecture to Cisco Software Licensing (CSL). Smart Licensing uses the Cisco Smart Software Manager as a backend tool for managing licenses. Smart Call Home must be configured before using the Smart Licensing. By default, Smart Licensing and Smart Call Home are enabled on the Cisco cBR routers.

For more information about Smart Licensing, see Cisco Smart Licensing on the Cisco cBR Router.

How to Configure Call Home

Configuring Smart Call Home (Single Command)

Smart Call Home is enabled by default on the router. The CiscoTAC-1 profile to send data to Cisco is also enabled by default.

You do not need to use the single command to enable Smart Call Home on the router unless you need to change to anonymous mode or add HTTP proxy using the single command.

To enable all Call Home basic configurations using a single command, perform the following steps:

Procedure

  Command or Action Purpose

Step 1

configure terminal

Example:


Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home reporting { anonymous | contact-email-addr email-address } [ http-proxy { ipv4-address | ipv6-address | name } port port number ]

Example:


Device(config)# 
call-home reporting contact-email-addr email@company.com
Enables all Call Home basic configurations using a single command.

  • anonymous —Enables Call-Home TAC profile to only send crash, inventory, and test messages and send the messages in an anonymous way.

  • contact-email-addr —Enables Smart Call Home service full reporting capability and sends a full inventory message from Call-Home TAC profile to Smart Call Home server to start full registration process.

  • http-proxy { ipv4-address | ipv6-address | name —An ipv4 or ipv6 address or server name. Maximum length is 64.

  • port port number —Port number. Range is 1 to 65535.

Note

 

HTTP proxy option allows you to make use of your own proxy server to buffer and secure internet connections from your devices.

Note

 

After successfully enabling Call Home either in anonymous or full registration mode using the call-home reporting command, an inventory message is sent out. If Call Home is enabled in anonymous mode, an anonymous inventory message is sent out. If Call Home is enabled in full registration mode, a Full Inventory message for full registration mode is sent. For more information about what is sent in these messages, see Alert Groups Trigger Events and Commands.

Configuring Call Home

For security reasons, we recommend that you use the HTTPS transport options, due to the additional payload encryption that HTTPS offers. The Transport Gateway software is downloadable from Cisco.com and is available if you require an aggregation point or a proxy for connection to the Internet.

The implementation on the router supports the trustpool feature (embedded CA certificates in IOS images). The trustpool feature simplifies configuration to enable Smart Call Home service on configured devices. It eliminates the requirement of manually configuring the trustpool and provides automatic update of the CA certificate should it change in the future.

Enabling and Disabling Call Home

To enable or disable the Call Home feature, complete the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Router# 
configure terminal

Enters global configuration mode.

Step 2

service call-home

Example:

Router(config)# 
service call-home

Enables the Call Home feature.

Step 3

no service call-home

Example:

Router(config)# 
no service call-home

Disables the Call Home feature.

Configuring Contact Information

Each router must include a contact e-mail address. You can optionally include a phone number, street address, contract ID, customer ID, and site ID.

To assign the contact information, complete the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Router> 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Router(config)# 
call-home

Enters call home configuration mode.

Step 3

contact-email-addr email-address

Example:

Router(cfg-call-home)# 
contact-email-addr username@example.com

Assigns the customer’s e-mail address. Enter up to 200 characters in e-mail address format with no spaces.

Step 4

phone-number + phone-number

Example:

Router(cfg-call-home)# 
phone-number +1-222-333-4444

(Optional) Assigns the customer’s phone number.

Note

 
The number must begin with a plus ( +) prefix, and may contain only dashes (-) and numbers. Enter up to 16 characters. If you include spaces, you must enclose your entry within double quotation marks (“ ”).

Step 5

street-address street-address

Example:

Router(cfg-call-home)# 
street-address “1234 Any Street, Any city, Any state, 12345”

(Optional) Assigns the customer’s street address where RMA equipment can be shipped. Enter up to 200 characters. If you include spaces, you must enclose your entry within double quotation marks (“ ”).

Step 6

customer-id text

Example:

Router(cfg-call-home)# 
customer-id Customer1234

(Optional) Identifies the customer ID. Enter up to 64 characters. If you include spaces, you must enclose your entry within double quotation marks (“ ”).

Step 7

site-id text

Example:

Router(cfg-call-home)# 
site-id Site1ManhattanNY

(Optional) Identifies the customer site ID. Enter up to 200 characters. If you include spaces, you must enclose your entry within double quotation marks (“ ”).

Step 8

contract-id text

Example:

Router(cfg-call-home)# 
contract-id Company1234

(Optional) Identifies the customer’s contract ID for the router. Enter up to 64 characters. If you include spaces, you must enclose your entry within double quotation marks (“ ”).

Configuring Destination Profiles

A destination profile contains the required delivery information for an alert notification. At least one destination profile is required. You can configure multiple destination profiles of one or more types.

You can create and define a new destination profile or copy and use the predefined destination profile. If you define a new destination profile, you must assign a profile name. You can control which profile to be used for Smart Licensing by enabling or disabling smart-licensing data of that profile. Only one active profile can have smart-license data enabled.


Note

If you use the Smart Call Home service, the destination profile must use the XML message format.

A destination profile includes the following information:

  • Profile name—String that uniquely identifies each user-defined destination profile. The profile name is limited to 31 characters and is not case-sensitive. You cannot use all as a profile name.

  • Transport method—Transport mechanism, either email or HTTP (including HTTPS), for delivery of alerts.

    • For user-defined destination profiles, email is the default, and you can enable either or both transport mechanisms. If you disable both methods, email is enabled.

    • For the predefined CiscoTAC-1 profile, you can enable either transport mechanism, but not both.

  • Destination address—The actual address related to the transport method by which the alert should be sent. You can change the destination of the CiscoTAC-1 profile.

  • Message formatting—The message format used for sending the alert. The format options for a user-defined destination profile are long-text, short-text, or XML. The default is XML. For the predefined CiscoTAC-1 profile, only XML is allowed.

  • Message size—The maximum destination message size. The valid range is 50 to 3,145,728 bytes. The default is 3,145,728 bytes.

  • Reporting method—You can choose which data to report for a profile. You can enable reporting of Smart Call Home data or Smart Licensing data, or both. Only one active profile is allowed to report Smart Licensing data at a time.

  • Anonymous reporting—You can choose for your customer identity to remain anonymous, and no identifying information is sent.

  • Subscribing to interesting alert-groups—You can choose to subscribe to alert-groups highlighting your interests.

  • Message severity level—The Call Home severity level that the alert must meet before a Call Home message is generated to all e-mail addresses in the destination profile. An alert is not generated if the Call Home severity level of the alert is lower than the message severity level set for the destination profile.

You can also configure a destination profile to allow periodic inventory update messages by using the inventory alert group.

A pre-defined destination profile CiscoTAC-1 is supported. It supports the XML message format. This profile is preconfigured with Cisco Smart Call Home server HTTPS URL, email address to reach the server, maximum message size, and message severity level for each alert group.


Important

We recommend that you do not use the message severity level 0. If you use message severity level 0, all syslogs will trigger Call Home messages, which can cause CPU and memory issues.

This section contains the following:

Creating a New Destination Profile
Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

profile name

Example:
Router(cfg-call-home)# profile profile1

Enters the Call Home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.

Step 5

destination transport-method { email | http }

Example:
Router(cfg-call-home-profile)# destination transport-method email

(Optional) Enables the message transport method.

  • email —Sets the e-mail message transport method.

  • http —Sets the HTTP message transport method.

Note

 

The no option disables the method.

Step 6

destination address { email email-address | http url }

Example:
Router(cfg-call-home-profile)# destination address email myaddress@example.com

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

Note

 

When entering a destination URL, include either http:// or https://, depending on whether the server is a secure server. If the destination is a secure server, you must also configure a trustpool CA.

Step 7

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

Example:
Router(cfg-call-home-profile)# destination preferred-msg-format xml

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

  • long-text —Configures the long text message format.

  • short-text —Configures the short text message format.

  • xml —Configures the XML message format.

Step 8

destination message-size bytes

Example:
Router(cfg-call-home-profile)# destination message-size 3,145,728

(Optional) Configures a maximum destination message size for the destination profile.

Step 9

active

Example:
Router(cfg-call-home-profile)# active

Enables the destination profile. By default, the profile is enabled when it is created.

If you activate a profile which enables smart-licensing data while smart-licensing data is already being reported in another active profile, you will receive an error message.

Step 10

reporting { all | smart-call-home-data | smart-licensing-data }

Example:
Router(cfg-call-home-profile)# reporting smart-call-home-data

Configures the type of data to report for a profile.

You can select either to report Smart Call Home data or Smart Licensing data. Selecting the all option reports data for both types of data.

Step 11

end

Example:
Router(cfg-call-home-profile)# end

Returns to privileged EXEC mode.

Step 12

show call-home profile { name | all }

Example:
Router# show call-home profile profile1

Displays destination profile configuration for specified profile or all configured profiles.

Step 13

show call-home smart-licensing

Example:
Router# show call-home smart-licensing

Displays the current Call Home Smart Licensing settings for the configured destination profiles.

Step 14

show call-home smart-licensing statistics

Example:
Router# show call-home smart-licensing statistics

Displays the Call Home Smart Licensing statistics.

Copying a Destination Profile

You can create a new destination profile by copying an existing profile

Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

copy profile source-profile target-profile

Example:
Router(cfg-call-home)# copy profile profile1 profile2

Creates a new destination profile with the same configuration settings as the existing destination profile.

  • source-profile —Name of the source destination profile.

  • target-profile —Name of the target or new destination profile.

Renaming a Destination Profile
Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

rename profile source-profile target-profile

Example:
Router(cfg-call-home)# rename profile profile1 profile2

Renames the existing destination profile.

  • source-profile —Name of the source destination profile.

  • target-profile —Name of the target destination profile.

Setting Profiles to Anonymous Mode
Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

profile name

Example:
Router(cfg-call-home)# profile profile1

Enters the Call Home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.

Step 5

anonymous-reporting-only

Example:
Router(cfg-call-home-profile)# anonymous-reporting-only

Sets the profile to anonymous mode.

Note

 

By default, the profile sends a full report of all types of events subscribed in the profile. When anonymous-reporting-only is set, only crash, inventory, and test messages are sent.

Subscribing to Alert Groups

An alert group is a predefined subset of Call Home alerts that are supported. You can select one or more alert groups to be received by a destination profile.

  • Configuration

  • Crash

  • Diagnostic

  • Environment

  • Inventory

  • Snapshot

  • Syslog

The triggering events for each alert group are listed in the Alert Group Trigger Events and Commands, and the contents of the alert group messages are listed in the Message Contents.

You can select one or more alert groups to be received by a destination profile.


Note

Call Home alerts are only sent to destination profiles that have subscribed to the alert group containing that Call Home alert. The alert group must be enabled. The Call Home event severity must be at or above the message severity set in the destination profile.

Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

alert-group { all | configuration | crash | diagnostic | environment | inventory | snapshot | syslog }

Example:
Router(cfg-call-home)# alert-group all

Enables the specified alert group. Use the keyword all to enable all alert groups. By default, all alert groups are enabled.

Step 5

profile name

Example:
Router(cfg-call-home)# profile profile1

Enters the Call Home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.

Step 6

subscribe-to-alert-group configuration [ periodic { daily hh:mm | monthly date hh:mm | weekly day hh:mm }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group configuration 
periodic daily 12:00

Subscribes this destination profile to the Configuration alert group. The Configuration alert group can be configured for periodic notification.

Step 7

subscribe-to-alert-group crash

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group crash

Subscribes to the Crash alert group in user profile. By default, Cisco TAC profile subscribes to the Crash alert group and cannot be unsubscribed.

Step 8

subscribe-to-alert-group diagnostic [ severity { catastrophic | disaster | fatal | critical | major | minor | warning | notification | normal | debugging }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group syslog severity major

Subscribes this destination profile to the Diagnostic alert group. The Diagnostic alert group can be configured to filter messages based on severity.

Step 9

subscribe-to-alert-group environment [ severity { catastrophic | disaster | fatal | critical | major | minor | warning | notification | normal | debugging }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group environment severity major

Subscribes this destination profile to the Environment alert group. The Environment alert group can be configured to filter messages based on severity.

Step 10

subscribe-to-alert-group inventory [ periodic { daily hh:mm | monthly date hh:mm | weekly day hh:mm }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group inventory 
periodic daily 12:00

Subscribes this destination profile to the Inventory alert group. The Inventory alert group can be configured for periodic notification

Step 11

subscribe-to-alert-group snapshot [ periodic { daily hh:mm | monthly date hh:mm | weekly day hh:mm | hourly mm | interval mm }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group snapshot 
periodic daily 12:00

Subscribes this destination profile to the Snapshot alert group. The Snapshot alert group can be configured for periodic notification.

By default, the Snapshot alert group has no command to run. You can add commands into the alert group. In doing so, the output of the commands added in the Snapshot alert group will be included in the snapshot message.

Step 12

subscribe-to-alert-group syslog [ severity { catastrophic | disaster | fatal | critical | major | minor | warning | notification | normal | debugging }] [ pattern string ]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group syslog severity major

Subscribes this destination profile to the Syslog alert group. The Syslog alert group can be configured to filter messages based on severity. You can specify a pattern to be matched in the syslog message. If the pattern contains spaces, you must enclose it in quotes ("").

You can specify a text pattern to be matched within each syslog message. If you configure a pattern, a Syslog alert group message is sent only if it contains the specified pattern and meets the severity threshold. If the pattern contains spaces, you must enclose it in quotes (“”). You can specify up to five patterns for each destination profile.

Step 13

subscribe-to-alert-group all

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group all

(Optional) Subscribes to all available alert groups.

Important

 

Entering this command causes the generation of a large number of syslog messages. We recommend that you subscribe to alert groups individually, using appropriate severity levels and patterns when possible.

Periodic Notification

When you subscribe a destination profile to either the Configuration, Inventory, or Snapshot alert group, you can choose to receive the alert group messages asynchronously or periodically at a specified time. The following time intervals are available:

  • Daily—Specify the time of day to send, using an hour:minute format hh:mm, with a 24-hour clock (for example, 14:30).

  • Weekly—Specify the day of the week and time of day in the format day hh:mm, where the day of the week is spelled out (for example, monday).

  • Monthly—Specify the numeric date, from 1 to 31, and the time of day, in the format date hh:mm.

  • Interval—Specifies the interval at which the periodic message is sent, from 1 to 60 minutes.

  • Hourly—Specifies the minute of the hour at which the periodic message is sent, from 0 to 59 minutes.


Note

Hourly and by interval periodic notifications are available for the Snapshot alert group only.

Message Severity Threshold

Call Home allows you to filter messages based on severity. You can associate each predefined or user-defined destination profile with a Call Home threshold from 0 (least urgent) to 9 (most urgent). The default is 0 (all messages are sent).

When you subscribe a destination profile to the Environment or Syslog alert group, you can set a threshold for relay of alert group messages based on the message severity level. Any message with a value lower than the destination profile threshold is not sent to the destination.

When you subscribe to an alert group in a destination profile with a specified severity, you subscribe to getting messages triggered by the events that have same or higher severity in that alert group.


Note

Subscribing to syslog message at low severity level is not recommended, as it would trigger too many syslog messages that might lower the system performance.


Note

Call Home severity levels are not the same as system message logging severity levels.

Table 2. Severity and Syslog Level Mapping

Smart Call Home Level

Keyword

syslog Level

Description

9

catastrophic

—

Network-wide catastrophic failure.

8

disaster

—

Significant network impact.

7

fatal

Emergency (0)

System is unusable.

6

critical

Alert (1)

Critical conditions that indicate that immediate attention is needed.

5

major

Critical (2)

Major conditions.

4

minor

Error (3)

Minor conditions.

3

warning

Warning (4)

Warning conditions.

2

notification

Notice (5)

Basic notification and informational messages. Possibly independently insignificant.

1

normal

Information (6)

Normal event signifying return to normal state.

0

debugging

Debug (7)

Debugging messages.

Syslog Pattern Matching

When you subscribe a destination profile to the Syslog alert group, you can optionally specify a text pattern to be matched within each syslog message. If you configure a pattern, a Syslog alert group message will be sent only if it contains the specified pattern and meets the severity threshold. If the pattern contains spaces, you must enclose it in quotes (" ") when configuring it. You can specify up to five patterns for each destination profile.

Configuring Snapshot Command List

To configure the snapshot command list, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters Call Home configuration mode.

Step 3

[ no | default ] alert-group-config snapshot

Example:

Device(cfg-call-home)# 
alert-group-config snapshot

Enters snapshot configuration mode.

The no or default command will remove all snapshot command.

Step 4

[ no | default ] add-command command string

Example:

Device(cfg-call-home-snapshot)# 
add-command
 
"show version"

Adds the command to the Snapshot alert group. The no or default command will remove the corresponding command.

  • command string —IOS command. Maximum length is 128.

Step 5

end

Example:

Device(cfg-call-home-snapshot)# 
exit

Exits and saves the configuration.

Configuring General email Options

Configuring the Mail Server

To use the e-mail message transport, you must configure at least one Simple Mail Transfer Protocol (SMTP) e-mail server address. You can specify up to four backup e-mail servers, for a maximum of five total mail-server definitions.

Consider the following guidelines when configuring the mail server:

  • Backup e-mail servers can be defined by repeating the mail-server command using different priority numbers.
  • The mail-server priority number parameter can be configured from 1 to 100. The server with the highest priority (lowest priority number) is tried first.

To configure general email options, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters call home configuration mode.

Step 3

mail-server { ipv4-address | name } priority number

Example:

Device(cfg-call-home)# 
mail-server stmp.example.com priority 1

Assigns an email server address and its relative priority among configured email servers.

Provide either of these:

  • The email server’s IP address or

  • The email server’s fully qualified domain name (FQDN) of 64 characters or less.

Assign a priority number between 1 (highest priority) and 100 (lowest priority).

Step 4

sender from email-address

Example:

Device(cfg-call-home)# 
sender from username@example.com

(Optional) Assigns the e-mail address that will appear in the from field in Call Home e-mail messages. If no address is specified, the contact e-mail address is used.

Step 5

sender reply-to email-address

Example:

Device(cfg-call-home)# 
sender reply-to username@example.com

(Optional) Assigns the e-mail address that will appear in the reply-to field in Call Home e-mail messages.

Step 6

source-interface interface-name

Example:

Device(cfg-call-home)# 
source-interface loopback1

Assigns the source interface name to send call-home messages.

interface-name —Source interface name. Maximum length is 64.

Note

 

For HTTP messages, use the ip http client source-interface interface-name command in global configuration mode to configure the source interface name. This allows all HTTP clients on the device to use the same source interface.

Step 7

source-ip-address ipv4/ipv6 address

Example:

Device(cfg-call-home)# 
ip-address 209.165.200.226

Assigns source IP address to send call-home messages.

  • ipv4/ipv6 address —Source IP (ipv4 or ipv6) address. Maximum length is 64.

Step 8

vrf vrf-name

Example:

Device(cfg-call-home)# 
vrf
 
vpn1

(Optional) Specifies the VRF instance to send call-home email messages. If no vrf is specified, the global routing table is used.

Note

 

For HTTP messages, if the source interface is associated with a VRF, use the ip http client source-interface interface-name command in global configuration mode to specify the VRF instance that will be used for all HTTP clients on the device.

Specifying Rate Limit for Sending Call Home Messages

To specify the rate limit for sending Call Home messages, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters call home configuration mode.

Step 3

rate-limit number

Example:

Device(cfg-call-home)# 
rate-limit 40

Specifies a limit on the number of messages sent per minute.

  • number —Range 1 to 60. The default is 20.

Specifying HTTP Proxy Server

To specify an HTTP proxy server for sending Call Home HTTP(S) messages to a destination, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# call-home

Enters call home configuration mode.

Step 3

http-proxy {ipv4-address | ipv6-address name } name

Example:

Device(config)# http-proxy 10.1.1.1 port 1

Specifies the proxy server for the HTTP request.

Enabling AAA Authorization to Run IOS Commands for Call Home Messages

To enable AAA authorization to run IOS commands that enable the collection of output for a Call Home message, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters call home configuration mode.

Step 3

aaa-authorization

Example:

Device(cfg-call-home)# 
aaa-authorization

Enables AAA authorization.

Note

 

By default, AAA authorization is disabled for Call Home.

Step 4

aaa-authorization [ username username ]

Example:

Device(cfg-call-home)# 
aaa-authorization username username

Specifies the username for authorization.

  • username user —Default username is callhome. Maximum length is 64.
Configuring Syslog Throttling

To enable or disable Call Home syslog message throttling and avoid sending repetitive Call Home syslog messages, perform the following steps:

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters call home configuration mode.

Step 3

[ no ] syslog-throttling

Example:

Device(cfg-call-home)# 
syslog-throttling

Enables or disables Call Home syslog message throttling and avoids sending repetitive Call Home syslog messages. By default, syslog message throttling is enabled.

Configuring Call Home Data Privacy

The data-privacy command scrubs data, such as passwords and IP addresses, from running configuration files to protect the privacy of customers. Enabling the data-privacy command can affect CPU utilization when scrubbing a large amount of data. Currently, show command output is not being scrubbed except for configuration messages in the show running-config all and show startup-config data.

Procedure
  Command or Action Purpose

Step 1

configure terminal

Example:

Device# 
configure terminal

Enters global configuration mode.

Step 2

call-home

Example:

Device(config)# 
call-home

Enters call home configuration mode.

Step 3

data-privacy { level {normal | high } | hostname }

Example:

Device(cfg-call-home)# 
data-privacy level high

Scrubs data from running configuration file to protect the privacy of the user. The default data-privacy level is normal.

Note

 

Enabling the data-privacy command can affect CPU utilization when scrubbing a large amount of data.

  • normal —Scrubs sensitive data such as passwords.
  • high —Scrubs all normal-level commands plus the IP domain name and IP address commands.
  • hostname —Scrubs all high-level commands plus the hostname command.

Note

 

Scrubbing the hostname from configuration messages can cause Smart Call Home processing failure on some platforms.

Sending Call Home Messages Manually

Sending a Call Home Test Message Manually

You can use the call-home test command to send a user-defined Call Home test message.

Procedure
Command or Action Purpose

call-home test [ “ test-message ” ] profile name

Example:

Router# 
call-home test profile profile1

Sends a test message to the specified destination profile. The user-defined test message text is optional, but must be enclosed in quotes (“ ”) if it contains spaces. If no user-defined message is configured, a default message is sent.

Sending Call Home Alert Group Messages Manually

Before you begin

  • Only the snapshot, crash, configuration, and inventory alert groups can be sent manually. Syslog alert groups cannot be sent manually.

  • When you manually trigger a snapshot, configuration, or inventory alert group message and you specify a destination profile name, a message is sent to the destination profile regardless of the profile's active status, subscription status, or severity setting.

  • When you manually trigger a snapshot, configuration, or inventory alert group message and do not specify a destination profile name, a message is sent to all active profiles that have either a normal or periodic subscription to the specified alert group.

Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

call-home send alert-group snapshot [ profile name ]

Example:
Router# call-home send alert-group snapshot profile profile1

Sends a snapshot alert group message to one destination profile if specified, or to all subscribed destination profiles.

Step 3

call-home send alert-group crash [ profile name ]

Example:
Router# call-home send alert-group configuration profile profile1

Sends a crash alert group message to one destination profile if specified, or to all subscribed destination profiles.

Step 4

call-home send alert-group configuration [ profile name ]

Example:
Router# call-home send alert-group configuration profile profile1

Sends a configuration alert group message to one destination profile if specified, or to all subscribed destination profiles.

Step 5

call-home send alert-group inventory [ profile name ]

Example:
Router# call-home send alert-group inventory

Sends an inventory alert group message to one destination profile if specified, or to all subscribed destination profiles.

Submitting Call Home Analysis and Report Requests

You can use the call-home request command to submit information about your system to Cisco Systems to receive helpful analysis and report information specific to your system. You can request a variety of reports, including security alerts, known bugs, best practices, and command references.

Note the following guidelines when manually sending Call Home analysis and report requests:

  • If a profile name is specified, the request is sent to the profile. If no profile is specified, the request is sent to the Cisco TAC profile. The recipient profile does not need to be enabled for the call-home request. The profile should specify the e-mail address where the transport gateway is configured so that the request message can be forwarded to the Cisco TAC and the user can receive the reply from the Smart Call Home service.
  • The ccoid user-id is the registered identifier of the Smart Call Home user. If the user-id is specified, the response is sent to the e-mail address of the registered user. If no user-id is specified, the response is sent to the contact e-mail address of the device.
  • Based on the keyword specifying the type of report requested, the following information is returned:
    • config-sanity —Information on best practices as related to the current running configuration.
    • bugs-list —Known bugs in the running version and in the currently applied features.
    • command-reference —Reference links to all commands in the running configuration.
    • product-advisory —Product Security Incident Response Team (PSIRT) notices, End of Life (EOL) or End of Sales (EOS) notices, or field notices (FN) that may affect devices in your network.

To submit a request for analysis and report information from the Cisco Output Interpreter tool, complete the following steps:

Procedure
  Command or Action Purpose

Step 1

call-home request output-analysis “ show-command ”

Example:

[
profile
 

  

name
 ] [
ccoid
  
user-id
 ]
Example:

Device# 
call-home request output-analysis “show diag” profile TG

Sends the output of the specified show command for analysis. The show command must be contained in quotes (“”).

Step 2

call-home request { config-sanity | bugs-list | command-reference | product-advisory }

Example:

[
profile
 

  

name
 ] [
ccoid
  
user-id
 ]
Example:

Device#
 call-home request config-sanity profile TG

Sends the output of a predetermined set of commands, such as the show running-config all and show version commands, for analysis. In addition, the call home request product-advisory subcommand includes all inventory alert group commands. The keyword specified after the call-home request command specifies the type of report requested.

Manually Sending Command Output Message for One Command or a Command List

You can use the call-home send command to execute a CLI command and e-mail the command output to Cisco or to an e-mail address that you specify.

Note the following guidelines when sending the output of a command:

  • The specified IOS command or list of IOS commands can be any run command, including commands for all modules. The command must be contained in quotes (“”).

  • If the email option is selected using the “email” keyword and an email address is specified, the command output is sent to that address. If neither the email nor the HTTP option is specified, the output is sent in long-text format with the specified service request number to the Cisco TAC (attach@cisco.com).

  • If neither the “email” nor the “http” keyword is specified, the service request number is required for both long-text and XML message formats and is provided in the subject line of the email.

  • If the HTTP option is specified without a profile name or destination URL, the CiscoTac-1 profile destination HTTP or HTTPS URL is used as the destination. The destination email address can be specified so that Smart Call Home can forward the message to the email address. The user must specify either the destination email address or an SR number but they can also specify both.

  • If a profile is specified and the profile has callhome@cisco.com as one of its email destination, you must use XML as the message format. If you use long-text format, an error message is displayed.

To execute a command and send the command output, complete the following step:

Procedure
Command or Action Purpose

Use one of the following commands:

  • call-home send { cli command | cli list} [email [profile profile-name | email] [ msg-format { long-text | xml}]] [ tac-sevice-request SR#]
  • call-home send { cli command | cli list} [ http [ profile profile-name | URL-dest] [ destination-email-address email]] [ tac-sevice-request SR#]
Example:

Router# call-home send “show version;show running-config show inventory” email support@example.com msg-format xml

Executes the CLI or CLI list and sends output via email or HTTP.

  • {cli command | cli list }—Specifies the IOS command or list of IOS commands (separated by ‘;’). It can be any run command, including commands for all modules. The commands must be contained in quotes (“”).
  • email [profile profile-name | email] [ msg-format {long-text | xml}] —If the email option is selected and a profile name is specified, the command output will be sent to the email address configured in the profile. If an email address is specified, the command output will be sent to the specified email address. The message is in long-text or XML format with the service request number in the subject. The profile name or email address, the service request number, or both must be specified. The service request number is required if the profile name or email address is not specified (default is attach@cisco.com for long-text format and callhome@cisco.com for XML format).

  • http [ profile profile-name | URL-dest] [ destination-email-address email] —If the http option is selected without a profile name or destination URL, the command output will be sent to Smart Call Home backend server (URL specified in TAC profile) in XML format. If a profile name or destination URL is specified, the command output will be sent to the destination URLs configured in the profile (profile-name case) or the destination URL specified in the command.

    destination-email-address email can be specified so that the backend server can forward the message to the email address. The email address, the service request number, or both must be specified.

  • tac-service-request SR# —Specifies the service request number. The service request number is required if the email address is not specified.

Configuring Diagnostic Signatures

The Diagnostic Signatures feature downloads digitally signed signatures to devices. Diagnostic Signatures (DS) files are formatted files that collate knowledge of diagnostic events and provide methods to troubleshoot them without a need to upgrade the Cisco software. The aim of DS is to deliver flexible intelligence that can detect and collect troubleshooting information that can be used to resolve known problems in customer networks.

Prerequisites for Diagnostic Signatures

Before you download and configure diagnostic signatures (DSes) on a device, you must ensure that the following conditions are met:

  • You must assign a DS to the device. Refer to the “Diagnostic Signature Downloading” section for more information on how to assign DSes to devices.

  • HTTP/Secure HTTP (HTTPS) transport is required for downloading DS files. You must install the certification authority (CA) certificate to enable the authentication of the destination HTTPS server.


Note

If you configure the trustpool feature, the CA certificate is not required.

Information About Diagnostic Signatures

Diagnostic Signature Overview

Diagnostic signatures (DS) for the Call Home system provides a flexible framework that allows the defining of new events and corresponding CLIs that can analyze these events without upgrading the Cisco software.

DSs provide the ability to define more types of events and trigger types than the standard Call Home feature supports. The DS subsystem downloads and processes files on a device as well as handles callbacks for diagnostic signature events.

The Diagnostic Signature feature downloads digitally signed signatures that are in the form of files to devices. DS files are formatted files that collate the knowledge of diagnostic events and provide methods to troubleshoot these events.

DS files contain XML data to specify the event description, and these files include CLI commands or scripts to perform required actions. These files are digitally signed by Cisco or a third party to certify their integrity, reliability, and security.

The structure of a DS file can be one of the following formats

  • Metadata-based simple signature that specifies the event type and contains other information that can be used to match the event and perform actions such as collecting information by using the CLI. The signature can also change configurations on the device as a workaround for certain bugs.

  • Embedded Event Manager (EEM) Tool Command Language (Tcl) script-based signature that specifies new events in the event register line and additional action in the Tcl script.

  • Combination of both the formats above.

The following basic information is contained in a DS file:

  • ID (unique number)—unique key that represents a DS file that can be used to search a DS.

  • Name (ShortDescription)—unique description of the DS file that can be used in lists for selection.

  • Description—long description about the signature.

  • Revision—version number, which increments when the DS content is updated.

  • Event & Action—defines the event to be detected and the action to be performed after the event happens.

Diagnostic Signature Downloading

To download the diagnostic signature (DS) file, you require the secure HTTP (HTTPS) protocol. If you have already configured an email transport method to download files on your device, you must change your assigned profile transport method to HTTPS to download and use DS.

Cisco software uses a PKI Trustpool Management feature, which is enabled by default on devices, to create a scheme to provision, store, and manage a pool of certificates from known certification authorities (CAs). The trustpool feature installs the CA certificate automatically. The CA certificate is required for the authentication of the destination HTTPS servers.

There are two types of DS update requests to download DS files: regular and forced-download.

Regular download requests DS files that were recently updated. You can trigger a regular download request either by using a periodic configuration or by initiating an on-demand CLI. The regular download update happens only when the version of the requested DS is different from the version of the DS on the device. Periodic download is only started after there is any DS assigned to the device from DS web portal. After the assignment happens, the response to the periodic inventory message from the same device will include a field to notify device to start its periodic DS download/update. In a DS update request message, the status and revision number of the DS is included such that only a DS with the latest revision number is downloaded.

Forced-download downloads a specific DS or a set of DSes. You can trigger the forced-download update request only by initiating an on-demand CLI. In a force-download update request, the latest version of the DS file is downloaded irrespective of the current DS file version on the device.

The DS file is digitally signed, and signature verification is performed on every downloaded DS file to make sure it is from a trusted source.

Diagnostic Signature Signing

The diagnostic signature (DS) files are digitally signed before they are made available for downloading. The following methods are used for digitally signing DS files:

  • Signing algorithm (Rivest Shamir and Adleman [RSA] 2048 bits)

  • Request keypairs to Abraxas system, which is the digital signing client

  • DS signed via secure socket layer (SSL) through a code signing client, where the signature is embedded using XML tags

  • Public keys are embedded in the DS subsystem (Cisco signed, partner signed, third-party signed) in the Cisco software. The digitally signed DS file contains the product name such as Diagnostic_Signatures (Cisco signed), Diagnostic_Signatures_Partner, Diagnostic_Signatures_3rd_Party. The product names are only used to sign the DS files.

The digital signing client can be found at https://abraxas.cisco.com/SignEngine/submit.jsp

These conditions that must be met to verify the digital signature in a DS file:

  • Code sign component support must be available in Cisco software.

  • Various public keys that verify the different kinds of diagnostic signatures must be included in platforms where DS is supported.

  • After parsing and retrieving the DS, the DS must execute the verification application program interface (API) to verify that the DS is valid.

Diagnostic Signature Workflow

The diagnostic signature feature is enabled by default in Cisco software. The following is the workflow for creating diagnostic signatures:

  1. Find the DSs you want to download and assign them to the device. This step is mandatory for regular periodic download, but not required for forced download.

  2. The device downloads all assigned DS(es) or a specific DS by regular periodic download or by on-demand forced download.

  3. The device verifies the digital signature of every single DS. If verification passes, the device stores the DS file into a non-removable disk, such as bootflash or hard disk, so that DS files can be read after the device is reloaded. On the routers, the DS file is stored in the bootflash:/call home directory.

  4. The device continues sending periodic regular DS download requests to get the latest revision of DS and replace the older one in device.

  5. The device monitors the event and executes the actions defined in the DS when the event happens.

Diagnostic Signature Events and Actions

The events and actions sections are the key areas used in diagnostic signatures. The event section defines all event attributes that are used for event detection. The action section lists all actions which should be performed after the event happens, such as collecting show command outputs and sending them to Smart Call Home to parse.

Diagnostic Signature Event Detection

Event detection in a DS is defined in two ways: single event detection and multiple event detection.

Single Event Detection

In single event detection, only one event detector is defined within a DS. The event specification format is one of the following two types:

  • DS event specification type: syslog, periodic, configuration, Online Insertion Removal (OIR) immediate, and callhome are the supported event types, where “immediate” indicates that this type of DS does not detect any events, its actions are performed once it is downloaded, and the call-home type modifies the current CLI commands defined for existing alert-group.

  • The Embedded Event Manager (EEM) specification type: supports any new EEM event detector without having to modify the Cisco software.

    Other than using EEM to detect events, a DS is triggered when a Tool Command Language (Tcl) script is used to specify event detection types.

Multiple Event Detection

Multiple event detection involves defining two or more event detectors, two ore more corresponding tracked object states, and a time period for the events to occur. The specification format for multiple event detection can include complex event correlation for tracked event detectors. For example, three event detectors (syslog, OIR, and IPSLA) are defined during the creation of a DS file. The correlation that is specified for these event detectors is that the DS will execute its action if both syslog and OIR events are triggered simultaneously, or if IPSLA is triggered alone.

Diagnostic Signature Actions

The diagnostic signature (DS) file consists of various actions that must be initiated when an evnt occurs. The action type indicates the kind of action that will be initiated in response to a certain event.

Variables are elements within a DS file that are used to customize the files.

DS actions are categorized into the following five types:
  • call-home
  • command
  • emailto
  • script
  • message

DS action types call-home and emailto collect event data and send a message to call-home servers or to the defined email addresses. The message uses "diagnostic-signature" as its message type and DS ID as the message sub-type.

The commands defined for the DS action type initiate CLI commands that can change configuration of the device, collect show command outputs, or run any EXEC command on the device. The DS action type script executes Tcl scripts.

DS action type message defines action to generate message to notify or remind user certain important information. The message could be broadcasted to all TTY lines or generated as a syslog entry.

Action Types

DS actions are categorized into the following four types:

  • Call-home

  • Command

  • Emailto

  • Script

DS action types call-home and emailto collect event data and send a message to call-home servers or to the defined email addresses. The message includes the following elements:

  • Message type—diagnostic-signature

  • Message subtype—ds-id

  • Message description—event-id : ds name

The commands defined for the DS action type initiates CLI commands that can change configuration of the device. The DS action type script executes Tcl scripts.

Diagnostic Signature Variables

Variables are referenced within a DS and are used to customize the DS file. All DS variable names have the prefix ds_ to separate them from other variables. The following are the supported DS variable types:

  • System variable: variables assigned automatically by the device without any configuration changes. The Diagnostic Signatures feature supports two system variables: ds_hostname and ds_signature_id.
  • Environment variable: values assigned manually by using the environment variable-name variable-value command in call-home diagnostic-signature configuration mode. Use the show call-home diagnostic-signature command to display the name and value of all DS environment variables. If the DS file contains unresolved environment variables, this DS will stay in pending status until the variable gets resolved.
  • Prompt variable: values assigned manually by using the call-home diagnostic-signature install ds-id command in privileged EXEC mode. If you do not set this value, the status of the DS indicates pending.
  • Regular expression variable: values assigned from a regular expression pattern match with predefined CLI command outputs. The value is assigned during the DS run.
  • Syslog event variable: values assigned during a syslog event detection in the DS file. This variable is valid only for syslog event detection.

How to Configure Diagnostic Signatures

Configuring the Service Call Home for Diagnostic Signatures

Configure the Service Call Home feature to set attributes such as the contact email address where notifications related with diagnostic signatures (DS) are sent and destination HTTP/secure HTTP (HTTPS) URL to download the DS files from.

You can also create a new user profile, configure correct attributes and assign it as the DS profile. For periodic downloads, the request is sent out just following full inventory message. By changing the inventory periodic configuration, the DS periodic download also gets rescheduled.


Note

The predefined CiscoTAC-1 profile is enabled as a DS profile by default and Cisco recommends using it. If used, you only need to change the destination transport-method to the http setting.

Before you begin

Before you download and configure diagnostic signatures (DSs) on a device, you must ensure that the following conditions are met:

  • You must assign one or more DSs to the device.

  • HTTP/Secure HTTP (HTTPS) transport is required for downloading DS files. You must install the certification authority (CA) certificate to enable the authentication of the destination HTTPS server.


    Note

    If you configure the trustpool feature, the CA certificate is not required.

Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

service call-home

Example:
Router(config)# service call-home

Enables Call Home service on a device.

Step 4

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 5

contact-email-addr email-address

Example:
Router(cfg-call-home)# contact-email-addr username@example.com

Assigns customer's e-mail address. You can enter a maximum of 200 characters in e-mail address format with no spaces.

Note

 

You can use any valid e-mail address. You cannot use spaces.

Step 6

mail-server { ipv4-address | name } priority number

Example:
Router(cfg-call-home)# mail-server 10.1.1.1 priority 4

(Optional) Configures a Simple Mail Transfer Protocol (SMTP) email server address for Call Home. This command is only used when sending email is part of the actions defined in any DS.

Step 7

profile name

Example:
Router(cfg-call-home)# profile profile1

Enters the Call Home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created.

Step 8

destination transport-method { email | http }

Example:
Router(cfg-call-home-profile)# destination transport-method email

(Optional) Enables the message transport method.

  • email —Sets the e-mail message transport method.

  • http —Sets the HTTP message transport method.

Note

 

To configure diagnostic signatures, you must use the http option.

Step 9

destination address { email email-address | http url }

Example:
Router(cfg-call-home-profile)# destination address http https://tools.cisco.com/its/
service/oddce/services/DDCEService

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

Note

 

To configure diagnostic signatures, you must use the http option.

Step 10

subscribe-to-alert-group inventory [ periodic { daily hh:mm | monthly date hh:mm | weekly day hh:mm }]

Example:
Router(cfg-call-home-profile)# subscribe-to-alert-group inventory 
periodic daily 12:00

Subscribes this destination profile to the Inventory alert group. The Inventory alert group can be configured for periodic notification

Note

 

This command is used only for the periodic downloading of DS files.

What to do next

Set the profile configured in the previous procedure as the DS profile and configure other DS parameters.

Configuring Diagnostic Signatures

Before you begin

Configure the Service Call Home feature to set attributes for the Call Home profile. You can either use the default CiscoTAC-1 profile or use the newly-created user profile.

Procedure
  Command or Action Purpose

Step 1

enable

Example:
Router> enable

Enables privileged EXEC mode.

  • Enter your password, if prompted.

Step 2

configure terminal

Example:
Router# configure terminal

Enters global configuration mode.

Step 3

call-home

Example:
Router(config)# call-home

Enters Call Home configuration mode.

Step 4

diagnostic-signature

Example:
Router(cfg-call-home)# diagnostic-signature

Enters call-home diagnostic signature mode.

Step 5

profile ds-profile-name

Example:
Router(cfg-call-home-diag-sign)# profile user1

Specifies the destination profile on a device that DS uses.

Step 6

environment ds_env-var-name ds-env-var-value

Example:
Router(cfg-call-home-diag-sign)# environment ds_env1 envarval

Sets the environment variable value for DS on a device.

Step 7

end

Example:
Router(cfg-call-home-diag-sign)# end

Exits call-home diagnostic signature mode and returns to privileged EXEC mode.

Step 8

call-home diagnostic-signature {{ deinstall | download } { ds-id | all } | install ds-id }

Example:
Router# call-home diagnostic-signature download 6030

Downloads, installs, and uninstalls diagnostic signature files on a device.

Step 9

show call-home diagnostic-signature [ ds-id [ actions | events | prerequisite | prompt | variables ] | failure | statistics [ download ]]

Example:
Router# show call-home diagnostic-signature actions

Displays the call-home diagnostic signature information.

Verifying the Call Home Configuration

  • show call-home —Displays the Call Home configuration summary.

    Following is a sample output of the command: 

    Router# show call-home

Current call home settings:
    call home feature : enable
    call home message's from address: Not yet set up
    call home message's reply-to address: Not yet set up

    vrf for call-home messages: Not yet set up

    contact person's email address: sch-smart-licensing@cisco.com (default)

    contact person's phone number: Not yet set up
    street address: Not yet set up
    customer ID: Not yet set up
    contract ID: Not yet set up
    site ID: Not yet set up

    source ip address: Not yet set up
    source interface: TenGigabitEthernet4/1/1
    Mail-server[1]: Address: 173.36.13.143 Priority: 60
    http proxy: Not yet set up

    Diagnostic signature: enabled
    Profile: CiscoTAC-1 (status: ACTIVE)
 
    Smart licensing messages: enabled
    Profile: CiscoTAC-1 (status: ACTIVE)

    aaa-authorization: disable
    aaa-authorization username: callhome (default)
    data-privacy: normal
    syslog throttling: enable

    Rate-limit: 20 message(s) per minute

    Snapshot command[0]: show cable modem summary totalb
    Snapshot command[1]: show cable modem summary total

Available alert groups:
    Keyword                  State   Description
    ------------------------ ------- -------------------------------
    configuration            Enable  configuration info
    crash                    Enable  crash and traceback info
    diagnostic               Enable  diagnostic info
    environment              Enable  environmental info
    inventory                Enable  inventory info
    snapshot                 Enable  snapshot info
    syslog                   Enable  syslog info

Profiles:
    Profile Name: CiscoTAC-1
    Profile Name: test

  • show call-home detail —Displays the Call Home configuration in detail.

    Following is a sample output of the command: 

    Router# show call-home detail

Current call home settings:
    call home feature : enable
    call home message's from address: Not yet set up
    call home message's reply-to address: Not yet set up

    vrf for call-home messages: Not yet set up

    contact person's email address: sch-smart-licensing@cisco.com (default)

    contact person's phone number: Not yet set up
    street address: Not yet set up
    customer ID: Not yet set up
    contract ID: Not yet set up
    site ID: Not yet set up

    source ip address: Not yet set up
    source interface: TenGigabitEthernet4/1/1
    Mail-server[1]: Address: 173.36.13.143 Priority: 60
    http proxy: Not yet set up

    Diagnostic signature: enabled
    Profile: CiscoTAC-1 (status: ACTIVE)
 
    Smart licensing messages: enabled
    Profile: CiscoTAC-1 (status: ACTIVE)

    aaa-authorization: disable
    aaa-authorization username: callhome (default)
    data-privacy: normal
    syslog throttling: enable

    Rate-limit: 20 message(s) per minute

    Snapshot command[0]: show cable modem summary totalb
    Snapshot command[1]: show cable modem summary total

Available alert groups:
    Keyword                  State   Description
    ------------------------ ------- -------------------------------
    configuration            Enable  configuration info
    crash                    Enable  crash and traceback info
    diagnostic               Enable  diagnostic info
    environment              Enable  environmental info
    inventory                Enable  inventory info
    snapshot                 Enable  snapshot info
    syslog                   Enable  syslog info

Profiles:

Profile Name: CiscoTAC-1
    Profile status: ACTIVE
    Profile mode: Anonymous Reporting Only
    Reporting Data: Smart Call Home, Smart Licensing
    Preferred Message Format: xml
    Message Size Limit: 3145728 Bytes
    Transport Method: http
    Email address(es): callhome@cisco.com
    HTTP  address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService

    Periodic configuration info message is scheduled every 17 day of the month at 09:39

    Periodic inventory info message is scheduled every 17 day of the month at 09:24

    Alert-group               Severity
    ------------------------  ------------
    crash                     debug
    diagnostic                minor
    environment               minor
    inventory                 normal

    Syslog-Pattern            Severity
    ------------------------  ------------
    .*                        major

  • show call-home alert-group —Displays the available alert groups and their status.

    Following is a sample output of the command: 

    Router# show call-home alert-group

Available alert groups:
    Keyword                  State   Description
    ------------------------ ------- -------------------------------
    configuration            Enable  configuration info
    crash                    Enable  crash and traceback info
    diagnostic               Enable  diagnostic info
    environment              Enable  environmental info
    inventory                Enable  inventory info
    snapshot                 Enable  snapshot info
    syslog                   Enable  syslog info

  • show call-home mail-server status —Checks and displays the availability of the configured email servers.

    Following is a sample output of the command: 

    Router# show call-home mail-server status    
    
    Mail-server[1]: Address: 173.36.13.143 Priority: 60

  • show call-home profile { all | name} —Displays the configuration of the specified destination profile. Use the keyword all to display the configuration of all destination profiles.

    Following is a sample output of the command: 

    Router# show call-home profile CiscoTac-1

Profile Name: CiscoTAC-1
    Profile status: ACTIVE
    Profile mode: Full Reporting
    Reporting Data: Smart Call Home, Smart Licensing
    Preferred Message Format: xml
    Message Size Limit: 3145728 Bytes
    Transport Method: email
    Email address(es): callhome@cisco.com
    HTTP  address(es): http://10.22.183.117:8080/ddce/services/DDCEService

    Periodic configuration info message is scheduled every 17 day of the month at 09:39

    Periodic inventory info message is scheduled every 17 day of the month at 09:24

    Alert-group               Severity
    ------------------------  ------------
    crash                     debug       
    diagnostic                minor       
    environment               minor       
    inventory                 normal      

    Syslog-Pattern            Severity
    ------------------------  ------------
    .*                        major

  • show call-home statistics [ detail | profile profile-name] —Displays the statistics of Call Home events.

    Following is a sample output of the command: 

    Router# show call-home statistics 

Message Types    Total                Email                HTTP
-------------   -------------------- -------------------- ------------------
Total Success   4                    3                    1                    
    Config      1                    1                    0                    
    Crash       0                    0                    0                    
    Diagnostic  0                    0                    0                    
    Environment 0                    0                    0                    
    Inventory   1                    0                    1                    
    Snapshot    0                    0                    0                    
    SysLog      2                    2                    0                    
    Test        0                    0                    0                    
    Request     0                    0                    0                    
    Send-CLI    0                    0                    0                    
    SCH         0                    0                    0

Total In-Queue  0                    0                    0 
    Config      0                    0                    0                    
    Crash       0                    0                    0                    
    Diagnostic  0                    0                    0                    
    Environment 0                    0                    0                    
    Inventory   0                    0                    0                    
    Snapshot    0                    0                    0                    
    SysLog      0                    0                    0                    
    Test        0                    0                    0                    
    Request     0                    0                    0                    
    Send-CLI    0                    0                    0                    
    SCH         0                    0                    0 

Total Failed    0                    0                    0                    
    Config      0                    0                    0                    
    Crash       0                    0                    0                    
    Diagnostic  0                    0                    0                    
    Environment 0                    0                    0                    
    Inventory   0                    0                    0                    
    Snapshot    0                    0                    0                    
    SysLog      0                    0                    0                    
    Test        0                    0                    0                    
    Request     0                    0                    0                    
    Send-CLI    0                    0                    0                    
    SCH         0                    0                    0                    

Total Ratelimit
      -dropped  0                    0                    0                    
    Config      0                    0                    0                    
    Crash       0                    0                    0                    
    Diagnostic  0                    0                    0                    
    Environment 0                    0                    0                    
    Inventory   0                    0                    0                    
    Snapshot    0                    0                    0                    
    SysLog      0                    0                    0                    
    Test        0                    0                    0                    
    Request     0                    0                    0                    
    Send-CLI    0                    0                    0                    
    SCH         0                    0                    0                    

Last call-home message sent time: 2015-03-06 18:21:49 GMT+00:00

  • show call-home diagnostic-signature —Displays the configuration of diagnostic signature information.

    Following is a sample output of the command: 

    Router# show call-home diagnostic-signature

Current diagnostic-signature settings:
 Diagnostic-signature: enabled
 Profile: CiscoTAC-1 (status: ACTIVE)
 Environment variable:
           Not yet set up

Downloaded DSes:
                                                             Last Update
DS ID    DS Name                         Revision Status     (GMT-05:00)
-------- ------------------------------- -------- ---------- -------------------

  • show call-home version —Displays the Call Home version information.

    Following is a sample output of the command: 

    Router# show call-home version

Call-Home Version 3.0
Component Version:
 call-home: (rel4)1.0.15
 eem-call-home: (rel2)1.0.5

Configuration Example for Call Home

Example: Call Home Configuration

Following is a configuration example for configuring the HTTPS transport : 



ip host tools.cisco.com 72.163.4.38
vrf definition smart-vrf
 !
 address-family ipv4
 exit-address-family
 !
 address-family ipv6
 exit-address-family
!
interface TenGigabitEthernet4/1/1
 vrf forwarding smart-vrf
 ip address 172.22.11.25 255.255.255.128
 no ip proxy-arp
!
ip route vrf smart-vrf 72.163.4.38 255.255.255.255 172.22.11.1
!
ip http client source-interface TenGigabitEthernet4/1/1
!

Following is a configuration example for configuring email options: 


call-home
 mail-server 173.36.13.143 priority 60
 source-interface TenGigabitEthernet4/1/1
 vrf smart-vrf
 alert-group-config snapshot
  add-command "show cable modem summary total"
 profile "test"
  active
  destination transport-method email
  destination address email call-home@cisco.com
  subscribe-to-alert-group configuration
  subscribe-to-alert-group crash
  subscribe-to-alert-group diagnostic severity debug
  subscribe-to-alert-group environment severity debug
  subscribe-to-alert-group inventory
  subscribe-to-alert-group syslog severity major pattern .*
  subscribe-to-alert-group syslog severity notification pattern "^.+UPDOWN.+changed state to (down|up)$"
  subscribe-to-alert-group snapshot periodic daily 12:00
!
ip route vrf smart-vrf 173.36.13.143 255.255.255.255 172.22.11.1
!

Example: Configuring HTTP Transport for Call Home on the Cisco cBR Series Router

Procedure

Step 1

Back up the current running configuration file.

Step 2

Verify the built-in router certificates.

Example:

Router# show crypto pki trustpool | include Class 3 Public

    ou=Class 3 Public Primary Certification Authority
    ou=Class 3 Public Primary Certification Authority

Step 3

(Optional) Configure VRF.

Example:

Router(config)# vrf def smart-vrf
Router(config-vrf)# address-family ipv4
Router(config-vrf-af)# exit-address-family
Router(config-vrf)# address-family ipv6
Router(config-vrf-af)# exit-address-family

Step 4

Set up the network interface.

Example:

Router(config)# interface TenGigabitEthernet4/1/1
Router(config)# vrf forward smart-vrf
Router(config-if)# ip address 172.22.11.25 255.255.255.128
Router(config-if)# no ip proxy-arp
Router(config-if)# no shut

Note

 

If IPv6 is enabled, you must configure IPv6 address.

Step 5

Set up the Cisco portal.

Example:

Router(config)# ip host tools.cisco.com 72.163.4.38
Router(config)# ip route vrf smart-vrf 72.163.4.38 255.255.255.255 172.22.11.1

Step 6

Verify the data path.

Example:

!Verify the connectivity to TenGigabitEthernet4/1/1 interface
Router# ping vrf smart-vrf 172.22.11.25

!Verify the connectivity to TenGigabitEthernet4//1/1 gateway
Router# ping vrf smart-vrf 172.22.11.1

!Verify the connectivity to tools.cisco.com
Router# ping vrf smart-vrf 72.163.4.38

Step 7

Configure the HTTP client interface.

Example:

Router(config)# ip http client source-interface TenGigabitEthernet4/1/1

Step 8

Send the Call Home alert group message manually and verify the configuration.

Example:

Router# call-home send alert inventory profile CiscoTAC-1

Sending inventory info call-home message ...
Please wait. This may take some time ...

Router# show call-home statistics | include Total
Message Types    Total                Email                HTTP
Total Success   0                    0                    0
Total In-Queue  1                    0                    1
Total Failed    0                    0                    0
Total Ratelimit

Router# show call-home statistics | include Total
Message Types    Total                Email                HTTP
Total Success   1                    0                    1
Total In-Queue  0                    0                    0
Total Failed    0                    0                    0
Total Ratelimit

Step 9

Display the Call Home configuration.

Example:

Router# show call-home profile CiscoTAC-1

Profile Name: CiscoTAC-1
    Profile status: ACTIVE
    Profile mode: Full Reporting
    Reporting Data: Smart Call Home, Smart Licensing
    Preferred Message Format: xml
    Message Size Limit: 3145728 Bytes
    Transport Method: http
    Email address(es): callhome@cisco.com
    HTTP  address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService

    Periodic configuration info message is scheduled every 15 day of the month at 15:37

    Periodic inventory info message is scheduled every 15 day of the month at 15:22
Alert-group               Severity
    ------------------------  ------------
    crash                     debug       
    diagnostic                minor       
    environment               minor       
    inventory                 normal      

    Syslog-Pattern            Severity
    ------------------------  ------------
    .*                        major

Example: Configuring Email Transport for Call Home on the Cisco cBR Series Router

Procedure

Step 1

Back up the current running configuration file.

Step 2

(Optional) Configure VRF.

Example:

Router(config)# vrf def smart-vrf
Router(config-vrf)# address-family ipv4
Router(config-vrf-af)# exit-address-family
Router(config-vrf)# address-family ipv6
Router(config-vrf-af)# exit-address-family

Step 3

Set up the network interface.

Example:

Router(config)# interface TenGigabitEthernet4/1/1
Router(config)# vrf forward smart-vrf
Router(config-if)# ip address 172.22.11.25 255.255.255.128
Router(config-if)# no ip proxy-arp
Router(config-if)# no shut

Note

 

If IPv6 is enabled, you must configure IPv6 address.

Step 4

Verify the data path.

Example:

!Verify the connectivity to TenGigabitEthernet4/1/1 interface
Router# ping vrf smart-vrf 172.22.11.25

!Verify the connectivity to TenGigabitEthernet4//1/1 gateway
Router# ping vrf smart-vrf 172.22.11.1

!Verify the connectivity to tools.cisco.com
Router# ping vrf smart-vrf 72.163.4.38

Step 5

(Optional) Configure Call Home.

Example:

Router(config)# call-home

!Configure the TenGigabitEthernet 4/1/1
Router(cfg-call-home)# source-ip-address 172.22.11.25

Step 6

Configure the mail server and verify the configuration.

Example:

Router(config)# call-home
Router(cfg-call-home)# mail-server 173.36.13.143 priority 60
Router(cfg-call-home)# vrf smart-vrf
Router(cfg-call-home)# exit
Router(config)# ip route vrf smart-vrf 173.36.13.143 255.255.255.255 172.22.11.1
Router(config)# end

Router# ping vrf smart-vrf 173.36.13.143
…

Router# show call-home mail status

Please wait. Checking for mail server status ...

Mail-server[1]: Address: 173.36.13.143 Priority: 60 [Available]

Note

 

The VRF configuration is optional.

Step 7

Create a new destination profile and subscribe to alert group.

Example:

Router(config)# call-home
Router(cfg-call-home)# alert-group-config snapshot
Router(cfg-call-home-snapshot)# add-command "show cable modem summary total”
Router(cfg-call-home-snapshot)# exit
Router(cfg-call-home)# profile test
Router(cfg-call-home-profile)# active
Router(cfg-call-home-profile)# destination transport-method email
Router(cfg-call-home-profile)# destination address email xyz@company.com
Router(cfg-call-home-profile)# subscribe syslog severity notification pattern "^.+UPDOWN.+changed state to (down|up)$”
Router(cfg-call-home-profile)# subscribe-to-alert-group snapshot periodic daily 12:00
Router(cfg-call-home-profile)# end

Step 8

Send the Call Home alert group message manually and verify the configuration.

Example:

Router# call-home send alert-group inventory profile test
Sending inventory info call-home message ...
Please wait. This may take some time ...

Router# show call-home statistics | include Total
Message Types    Total                Email                HTTP
Total Success   1                    0                    1                    
Total In-Queue  2                    2                    0                    
Total Failed    0                    0                    0                    
Total Ratelimit

Router# show call-home statistics | include Total
Message Types    Total                Email                HTTP
Total Success   3                    2                    1                    
Total In-Queue  0                    0                    0                    
Total Failed    0                    0                    0
Total Ratelimit

Step 9

Display the Call Home configuration.

Example:

Router# show call-home profile test

Profile Name: test
    Profile status: ACTIVE
    Profile mode: Full Reporting
    Reporting Data: Smart Call Home
    Preferred Message Format: xml
    Message Size Limit: 3145728 Bytes
    Transport Method: email
    Email address(es): abcd@company.com
    HTTP  address(es): Not yet set up

    Periodic snapshot info message is scheduled daily at 12:00

    Alert-group               Severity
    ------------------------  ------------
    configuration             normal      
    crash                     debug       
    diagnostic                debug       
    environment               debug       
    inventory                 normal     
Syslog-Pattern            Severity
    ------------------------  ------------     
    ^.+UPDOWN.+changed state
     to (down|up)$            notification

Default Settings

Table 3. Default Call Home Parameters

Parameters

Default

Call Home feature status

Enabled

User-defined profile status

Active

Predefined CiscoTAC-1 profile status

Active

Transport method

HTTP

Message format type

XML

Alert group status

Enabled

Call Home message severity threshold

Debug

Message rate limit for messages per minute

20

AAA authorization

Disabled

Call Home syslog message throttling

Enabled

Data privacy level

Normal

Alert Groups Trigger Events and Commands

The table below lists the supported alert groups and the default command output included in Call Home messages generated for the alert group.

Table 4. Call Home Alert Groups, Events, and Actions

Alert Group

Call Home Trigger Event

Syslog Event

Severity

Description and Executed Commands

Configuration

—

—

normal

periodic

Periodic events related to configuration sent monthly.

Commands executed:

  • show platform

  • show version

  • show inventory

  • show running-config all

  • show startup-config

Crash

—

—

debug

Events generated by a crash on the router, such as Supervisor or line card crash.

Commands executed:

Crash traceback

  • show version

  • show logging

  • show region

  • show stack

Crash system

  • show version

  • show inventory

  • show logging

  • show region

  • show stack

  • more crashinfo-file

Crash module

  • show version

  • show inventory

  • show platform

  • show logging

  • show region

  • show stack

  • more crashinfo-file

Diagnostic

—

—

minor

Events generated by diagnostics.

Commands executed:

  • show platform

  • show version

  • show diagnostic event slot detail

  • show inventory

  • show buffers

  • show logging

  • show diagnostic events slot all

Environmental

FAN_FAILURE

CBR_PEM-6-FANOK

CBR_PEM-3- FANFAIL

minor

Events related to power, fan, and environment sensing elements, such as temperature alarms.

Commands executed:

  • show platform

  • show environment

  • show inventory

  • show logging

TEMPERATURE_ALARM

ENVIRONMENTAL -1-ALERT

POWER_SUPPLY_FAILURE

CBR_PEM-6-PEMOK

CBR_PEM-3- PEMFAIL

Inventory

OIR_REMOVE

OIR_INSERTION

—

normal

Inventory status that is provided whenever a unit is cold booted, or when FRUs are inserted or removed. This alert is considered a non-critical event, and the information is used for status and entitlement.

Command executed:

  • show platform

  • show version

  • show inventory oid

  • show diag all eeprom detail

  • show interfaces

  • show file systems

  • show bootflash: all

  • show data-corruption

  • show memory statistics

  • show process memory

  • show process cpu

  • show process cpu history

  • show license udi

  • show license detail

  • show buffers

  • show platform software proc slot monitor cycle

Snapshot

—

—

normal

User-generated CLI commands.

Syslog

—

—

major

Events generated by Syslog messages.

Commands executed:

  • show inventory

  • show logging

Test

—

—

normal

User-generated test message sent to the destination profile.

Commands executed:

  • show inventory

  • show platform

  • show version

Message Contents

Smart Call Home supports the following message formats:

  • Short Text Message Format

  • Common Fields for Full Text and XML Messages

  • Fields Specific to Alert Group Messages for Full Text and XML Messages

  • Inserted Fields for a Reactive and Proactive Event Message

  • Inserted Fields for an Inventory Event Message

  • Inserted Fields for a User-Generated Test Message

The table below describes the short text formatting option for all message types.

Table 5. Short Text Message Format
Data Item Description
Device identification Configured device name
Date/time stamp Time stamp of the triggering event
Error isolation message Plain English description of triggering event
Alarm urgency level Error level such as that applied to system message

The table below describes the first set of common event message fields for full text or XML messages.

Table 6. Common Fields for Full Text and XML Messages
Data Item (Plain Text and XML) Description (Plain Text and XML) Call-Home Message Tag (XML Only)
Time stamp Date and time stamp of event in ISO time notation:

YYYY-MM-DD HH:MM:SS GMT+HH:MM.

CallHome/EventTime
Message name Name of message. For short text message only
Message type Name of message type, specifically "Call Home". CallHome/Event/Type
Message subtype Specific type of message: full, delta, test CallHome/Event/SubType
Message group Name of alert group, specifically "reactive". Optional, because default is "reactive". . For long-text message only
Severity level Severity level of message Body/Block/Severity
Source ID Product type for routing through the workflow engine. This is typically the product family name. For long-text message only
Device ID Unique device identifier (UDI) for the end device that generated the message. This field should be empty if the message is nonspecific to a device. The format is type@Sid@serial.
  •  type is the product model number from the backplane IDPROM.
  •  @ is a separator character.
  •  Sid is C, identifying the serial ID as a chassis serial number·
  •  serial is the number identified by the Sid field.
An example is WS-C6509@C@12345678

CallHome/CustomerData/ContractData/DeviceId

Customer ID Optional user-configurable field used for contract information or other ID by any support service.

CallHome/CustomerData/ContractData/CustomerId

Contract ID Optional user-configurable field used for contract information or other ID by any support service.

CallHome/CustomerData/ContractData/ContractId

Site ID Optional user-configurable field used for Cisco-supplied site ID or other data meaningful to alternate support service.

CallHome/CustomerData/ContractData/SiteId

Server ID If the message is generated from the device, this is the unique device identifier (UDI) of the device. The format is type@Sid@serial.
  •  type is the product model number from the backplane IDPROM.
  •  @ is a separator character.
  •  Sid is C, identifying the serial ID as a chassis serial number.
  •  serial is the number identified by the Sid field.
An example is WS-C6509@C@12345678. 		For long text message only
Message description Short text that describes the error. CallHome/MessageDescription
Device name Node that experienced the event (hostname of the device).

CallHome/CustomerData/SystemInfo/NameName

Contact name Name of person to contact for issues associated with the node that experienced the event.

CallHome/CustomerData/SystemInfo/Contact

Contact e-mail E-mail address of person identified as the contact for this unit.

CallHome/CustomerData/SystemInfo/ContactEmail

Contact phone number Phone number of the person identified as the contact for this unit.

CallHome/CustomerData/SystemInfo/ContactPhoneNumber

Street address Optional field that contains the street address for RMA part shipments associated with this unit.

CallHome/CustomerData/SystemInfo/StreetAddress

Model name Model name of the device (the specific model as part of a product family name).

CallHome/Device/Cisco_Chassis/Model

Serial number Chassis serial number of the unit.

CallHome/Device/Cisco_Chassis/SerialNumber

Chassis part number Top assembly number of the chassis. /aml/body/chassis/partNo
System object ID System Object ID that uniquely identifies the system.

CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name=“sysObjectID”

System description System description for the managed element.

CallHome/Device/Cisco_Chassis/ AdditionalInformation/AD@name=“sysDescr”

The table below describes the fields specific to alert group messages for full text and XML. These fields may be repeated if multiple commands are executed for an alert group.

Table 7. Fields Specific to Alert Group Messages for Full Text and XML Messages
Data Item (Plain Text and XML) Description (Plain Text and XML) XML Tag (XML Only)
Command output name Exact name of the issued command. /aml/attachments/attachment/name
Attachment type Specific command output. /aml/attachments/attachment/type
MIME type Either plain text or encoding type. /aml/attachments/attachment/mime
Command output text Output of command automatically executed. /mml/attachments/attachment/atdata

The table below describes the reactive and proactive event message format for full text or XML messages.

Table 8. Inserted Fields for a Reactive and Proactive Event Message
Data Item (Plain Text and XML) Description (Plain Text and XML) XML Tag (XML Only)
Chassis hardware version Hardware version of chassis. /aml/body/chassis/hwVersion
Supervisor module software version Top-level software version. /aml/body/chassis/swVersion
Affected FRU name Name of the affected FRU that is generating the event message. /aml/body/fru/name
Affected FRU serial number Serial number of the affected FRU. /aml/body/fru/serialNo
Affected FRU part number Part number of the affected FRU. /aml/body/fru/partNo
FRU slot Slot number of the FRU that is generating the event message. /aml/body/fru/slot
FRU hardware version Hardware version of the affected FRU. /aml/body/fru/hwVersion
FRU software version Software version(s) that is running on the affected FRU. /aml/body/fru/swVersion

The table below describes the inventory event message format for full text or XML messages.

Table 9. Inserted Fields for an Inventory Event Message
Data Item (Plain Text and XML) Description (Plain Text and XML) XML Tag (XML Only)
Chassis hardware version Hardware version of the chassis. /aml/body/chassis/hwVersion
Supervisor module software version Top-level software version. /aml/body/chassis/swVersion
FRU name Name of the affected FRU that is generating the event message. /aml/body/fru/name
FRU s/n Serial number of the FRU. /aml/body/fru/serialNo
FRU part number Part number of the FRU. /aml/body/fru/partNo
FRU slot Slot number of the FRU. /aml/body/fru/slot
FRU hardware version Hardware version of the FRU. /aml/body/fru/hwVersion
FRU software version Software version(s) that is running on the FRU. /aml/body/fru/swVersion

The table below describes the user-generated test message format for full text or XML.

Table 10. Inserted Fields for a User-Generated Test Message
Data Item (Plain Text and XML) Description (Plain Text and XML) XML Tag (XML Only)
Process ID Unique process ID. /aml/body/process/id
Process state State of process (for example, running or halted). /aml/body/process/processState
Process exception Exception or reason code. /aml/body/process/exception

Sample syslog Alert Notification in XML Format 

<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope">
<soap-env:Header>
<aml-session:Session
xmlns:aml-session="http://www.cisco.com/2004/01/aml-session"
soap-env:mustUnderstand="true"
soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next">
<aml-session:To>http://tools.cisco.com/neddce/services/DDCEService</aml
-session:To>
<aml-session:Path>
<aml-session:Via>http://www.cisco.com/appliance/uri</aml-session:Via>
</aml-session:Path>
<aml-session:From>http://www.cisco.com/appliance/uri</aml-session:From>
<aml-session:MessageId>MA:FXS1739Q0NR:548F4417</aml-session:MessageId>
</aml-session:Session>
</soap-env:Header>
<soap-env:Body>
<aml-block:Block 
xmlns:aml-block="http://www.cisco.com/2004/01/aml-block">
<aml-block:Header>
<aml-block:Type>http://www.cisco.com/2005/05/callhome/syslog</aml-block
:Type>
<aml-block:CreationDate>2014-12-16 04:27:03
GMT+08:00</aml-block:CreationDate>
<aml-block:Builder>
<aml-block:Name>CBR8</aml-block:Name>
<aml-block:Version>2.0</aml-block:Version>
</aml-block:Builder>
<aml-block:BlockGroup>
<aml-block:GroupId>GB:FXS1739Q0NR:548F4417</aml-block:GroupId>
<aml-block:Number>0</aml-block:Number>
<aml-block:IsLast>true</aml-block:IsLast>
<aml-block:IsPrimary>true</aml-block:IsPrimary>
<aml-block:WaitForPrimary>false</aml-block:WaitForPrimary>
</aml-block:BlockGroup>
<aml-block:Severity>6</aml-block:Severity>
</aml-block:Header>
<aml-block:Content>
<ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome"
version="1.0">
<ch:EventTime>2014-12-16 04:26:59 GMT+08:00</ch:EventTime> 
<ch:MessageDescription>Dec 16 04:26:59.885 CST: %ENVIRONMENTAL-1-ALERT:
Temp: INLET, Location: 6, State: Critical, Reading: 53 
Celsius</ch:MessageDescription> <ch:Event> <ch:Type>syslog</ch:Type> 
<ch:SubType></ch:SubType> <ch:Brand>Cisco Systems</ch:Brand>
<ch:Series>CBR8 Series Routers</ch:Series> </ch:Event> 
<ch:CustomerData> <ch:UserData> <ch:Email>xxxx@company.com</ch:Email>
</ch:UserData>
<ch:ContractData>
<ch:CustomerId></ch:CustomerId>
<ch:SiteId></ch:SiteId>
<ch:ContractId></ch:ContractId>
<ch:DeviceId>CBR-8-CCAP-CHASS@C@FXS1739Q0NR</ch:DeviceId>
</ch:ContractData>
<ch:SystemInfo>
<ch:Name>sig-cbr</ch:Name>
<ch:Contact></ch:Contact>
<ch:ContactEmail>xxxx@company.com</ch:ContactEmail>
<ch:ContactPhoneNumber></ch:ContactPhoneNumber>
<ch:StreetAddress></ch:StreetAddress>
</ch:SystemInfo>
<ch:CCOID></ch:CCOID>
</ch:CustomerData>
<ch:Device>
<rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0">
<rme:Model>CBR-8-CCAP-CHASS</rme:Model>
<rme:HardwareVersion>0.1</rme:HardwareVersion>
<rme:SerialNumber>FXS1739Q0NR</rme:SerialNumber>
<rme:AdditionalInformation>
<rme:AD name="PartNumber" value="000-00000-00" /> <rme:AD 
name="SoftwareVersion" value="15.5(20141214:005145) " /> <rme:AD 
name="SystemObjectId" value="1.3.6.1.4.1.9.1.2141" /> <rme:AD 
name="SystemDescription" value="Cisco IOS Software, IOS-XE Software 
(X86_64_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version
15.5(20141214:005145) [ece5_throttle_ios-ram-ece5-bk 105] Copyright (c) 
1986-2014 by Cisco Systems, Inc.
Compiled Sun 14-Dec-14 00:20 by ram" /> <rme:AD name="ServiceNumber" 
value="" /> <rme:AD name="ForwardAddress" value="" /> 
</rme:AdditionalInformation> </rme:Chassis> </ch:Device> </ch:CallHome> 
</aml-block:Content> <aml-block:Attachments> <aml-block:Attachment 
type="inline"> <aml-block:Name>show inventory</aml-block:Name> 
<aml-block:Data encoding="plain"> <![CDATA[show inventory Load for five 
secs: 2%/0%; one minute: 2%; five minutes: 2% Time source is NTP, 
04:27:02.278 CST Tue Dec 16 2014
NAME: "Chassis", DESCR: "Cisco cBR-8 CCAP Chassis"
PID: CBR-8-CCAP-CHASS  , VID: V01, SN: FXS1739Q0NR

NAME: "sup 0", DESCR: "Cisco cBR CCAP Supervisor Card"
PID: CBR-CCAP-SUP-160G , VID: V01, SN: CAT1736E05L

NAME: "harddisk 4/1", DESCR: "Hard Disk"
PID: UGB88RTB100HE3-BCU-DID, VID:    , SN: 11000072780

NAME: "sup-pic 4/1", DESCR: "Cisco cBR CCAP Supervisor Card PIC"
PID: CBR-SUPPIC-8X10G  , VID: V01, SN: CAT1735E004

NAME: "SFP+ module 4/1/0", DESCR: "iNSI xcvr"
PID: SFP+ 10GBASE-SR   , VID: A   , SN: FNS1727294V

NAME: "SFP+ module 4/1/1", DESCR: "iNSI xcvr"
PID: SFP+ 10GBASE-SR   , VID: A   , SN: FNS172727WZ

NAME: "SFP+ module 4/1/4", DESCR: "iNSI xcvr"
PID: 10GE ZR           , VID:     , SN: AGM120525EW

NAME: "sup 1", DESCR: "Cisco cBR CCAP Supervisor Card"
PID: CBR-CCAP-SUP-160G , VID: V01, SN: CAT1736E05L

NAME: "clc 6", DESCR: "Cisco cBR CCAP Line Card"
PID: CBR-CCAP-LC-40G   , VID: V01, SN: CAT1736E0EN

NAME: "Cable PHY Module", DESCR: "CLC Downstream PHY Module 6/0"
PID: cBR-8-GEMINI      , VID: V01 , SN: CSJ13152101

NAME: "Cable PHY Module", DESCR: "CLC Upstream PHY Module 6/2"
PID: cBR-8-LEOBEN      , VID: V01 , SN: TST98765432

NAME: "Power Supply Module 0", DESCR: "Cisco cBR CCAP AC Power Supply"
PID: PWR-3KW-AC-V2     , VID: V02, SN: DTM173702KQ

NAME: "Power Supply Module 2", DESCR: "Cisco cBR CCAP AC Power Supply"
PID: PWR-3KW-AC-V2     , VID: V02, SN: DTM173702GD


sig-cbr#]]></aml-block:Data>
</aml-block:Attachment>
<aml-block:Attachment type="inline">
<aml-block:Name>show logging</aml-block:Name> <aml-block:Data 
encoding="plain"> <![CDATA[show logging Load for five secs: 2%/0%; one 
minute: 2%; five minutes: 2% Time source is NTP, 04:27:02.886 CST Tue 
Dec 16 2014

Syslog logging: enabled (0 messages dropped, 51 messages rate-limited, 
0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.



No Inactive Message Discriminator.


    Console logging: level debugging, 213 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging:  level debugging, 262 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level informational, 209 message lines logged
        Logging Source-Interface:       VRF Name:

Log Buffer (1000000 bytes):

*Dec 15 20:20:16.188: Rommon debug: debugFlagsStr[7], flags[0x7] *Dec 
15 20:20:16.188: TRACE - Debug flag set 0x7 *Dec 15 20:20:16.188: TRACE 
- Register NV N:systemInitByEvent V:True with no CallBack *Dec 15 
20:20:16.188: TRACE - Register NV N:routingReadyByEvent V:True with no 
CallBack *Dec 15 20:20:16.188: TRACE - Smart agent init started.
Version=1.2.0_dev/22
*Dec 15 20:20:16.188: ERROR - PD init failed: The requested operation 
is not supported *Dec 15 20:20:16.188: ERROR - Pre Role Init Failed: 
The requested operation is not supported *Dec 15 20:20:16.188: TRACE - 
Smart agent init Done. status 10, state 4294967295, init 0 enable 0 
Current Role Invalid *Dec 15 20:20:16.188: TRACE - Shutdown Started 
*Dec 15 20:20:16.188: DEBUG - Scheduler shutdown start *Dec 15 
20:20:16.188: ERROR - Failed to set shutdown watched boolean (code 
Invalid argument (22)). Going the hard way!!!
*Dec 15 20:20:16.188: DEBUG - Destroying XOS stuff to exit dispatch 
loop *Dec 15 20:20:16.188: DEBUG - XDM dispatch loop about to exit *Dec 
15 20:20:16.188: DEBUG - Scheduler shutdown end *Dec 15 20:20:16.188: 
ERROR - SmartAgent not initialized.
*Dec 15 20:20:16.188: ERROR - Smart Agent not a RF client *Dec 15 
20:20:16.188: ERROR - Smart Agent not a CF client *Dec 15 20:20:16.188: 
TRACE - Setting Ha Mgmt Init FALSE *Dec 15 20:20:16.188: TRACE - 
Shutting down Any Role *Dec 15 20:20:17.432: (DBMS RPHA) Client 
initialization; status=success *Dec 15 20:20:17.432: CABLE Parser 
Trace:  cable_parser_init:82 *Dec 15 20:20:17.774: **** 
mcprp_ubr_punt_init: Initialized*****
-->RF_STATUS_SEND_RF_STATE received-->RF_PROG_INITIALIZATION received
*Dec 15 20:20:20.790: CWAN OIR debugging enabled (ROMMON variable 
DEBUG_CWAN_OIR set)-->RF_PROG_ACTIVE_FAST 
received-->RF_PROG_ACTIVE_DRAIN
received-->RF_PROG_ACTIVE_PRECONFIG 
received-->received-->RF_PROG_ACTIVE_POSTCONFIG
received-->RF_PROG_ACTIVE received
*Dec 15 20:20:20.841: **** IPC port 0x1000E created!
*Dec 15 20:20:20.841:  **** CIPC RP Server created UBRCCE_CIPC_14/0 !
*Dec 15 20:20:28.294: %SPANTREE-5-EXTENDED_SYSID: Extended SysId 
enabled for type vlan *Dec 15 20:20:31.944: %VOICE_HA-7-STATUS: CUBE 
HA-supported platform detected.
*Dec 15 20:20:33.391:  instant_msg_handle_proc_sup started!!
*Dec 15 20:20:33.391:  queue_msg_handle_proc_sup started!!
*Dec 15 20:20:35.603: %IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO: Management 
vrf Mgmt-intf created with ID 1, ipv4 table-id 0x1, ipv6 table-id
0x1E000001
*Dec 15 20:20:34.513: %IOSXE-6-PLATFORM: CLC4: cpp_cp: Process 
CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 15 20:20:03.806: %HW_PFU-3-PFU_IDPROM_CORRUPT: R0/0: cmand:  The 
PEM/FM idprom could be read, but is corrupt in slot P11 The system will 
run without environmental monitoring for this component *Dec 15 
20:20:09.012: %SYSTEM-3-SYSTEM_SHELL_LOG: R0/0:  2014/12/15
20:20:08 : <anon>
*Dec 15 20:20:13.919: %IOSXE-4-PLATFORM: R0/0: kernel: astro: FD open 
*Dec 15 20:20:13.919: %IOSXE-4-PLATFORM: R0/0: kernel: astro: astro:
mmio_start=d0000000 mmio_len=2000000
*Dec 15 20:20:13.919: %IOSXE-4-PLATFORM: R0/0: kernel: astro: Done 
astro Memory map base_ptr ffffc90016600000, astro_reg_ptr ffffc90016600000...
*Dec 15 20:20:16.259: %IOSXE-4-PLATFORM: R0/0: kernel: astro: FD open 
*Dec 15 20:20:16.553: %CPPHA-7-START: F0: cpp_ha:  CPP 0 preparing 
ucode *Dec 15 20:20:17.220: %CPPHA-7-START: F0: cpp_ha:  CPP 0 startup 
init *Dec 15 20:20:18.549: %PMAN-3-PROC_EMPTY_EXEC_FILE: F0: pvp.sh:  
Empty executable used for process iosdb *Dec 15 20:20:20.003: 
%PMAN-3-PROC_EMPTY_EXEC_FILE: CLC4: pvp.sh:  Empty executable used for 
process iosdb *Dec 15 20:20:20.783: %PMAN-3-PROC_EMPTY_EXEC_FILE: CLC4: 
pvp.sh:  Empty executable used for process iosdb *Dec 15 20:20:24.061: 
%HW_PFU-3-PFU_IDPROM_CORRUPT: R0/0: cmand:  The PEM/FM idprom could be 
read, but is corrupt in slot P11 The system will run without 
environmental monitoring for this component *Dec 15 20:20:31.722: 
%CPPHA-7-START: F0: cpp_ha:  CPP 0 running init *Dec 15 20:20:32.070: 
%CPPHA-7-READY: F0: cpp_ha:  CPP 0 loading and initialization complete 
*Dec 15 20:20:36.528 UTC: TRACE - Platform EventCB invoked. EventType: 
8 *Dec 15 20:20:36.528 UTC: DEBUG - Hostname changed. Old:sig-cbr 
New:sig-cbr *Dec 15 20:20:36.528 UTC: %CNS IQ:0.1 ID:0 
Changed:[sig-cbr] *Dec 15 20:20:36.528 UTC: %CNS IQ:0.2 ID:1 
Changed:[sig-cbr] *Dec 15 20:20:36.528 UTC: %CNS IQ:0.3 ID:2 
Changed:[sig-cbr] *Dec 15 20:20:36.594 UTC: %SYS-5-LOG_CONFIG_CHANGE: 
Buffer logging: level debugging, xml disabled, filtering disabled, size 
(1000000) *Dec 16 04:20:36.597 CST: %SYS-6-CLOCKUPDATE: System clock 
has been updated from 20:20:36 UTC Mon Dec 15 2014 to 04:20:36 CST Tue 
Dec 16 2014, configured from console by console.
*Dec 16 04:20:36.607 CST: spa_type 2946 ports 8 *Dec 16 04:20:36.622 
CST: spa_type 2946 ports 8 *Dec 16 04:20:37.350 CST: 
cmts_set_int_us_qos_flags: move US-QOS flags 0 to CDMAN *Dec 16 
04:20:37.350 CST: cmts_set_int_us_default_weights: move US-QOS weights 
to CDMAN *Dec 16 04:20:36.625 CST: %IOSXE-4-PLATFORM: R0/0: kernel: 
astro: FD open *Dec 16 04:20:43.221 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface Video6/0/0, changed state to up *Dec 16 
04:20:43.223 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Video6/0/1, changed state to up *Dec 16 04:20:43.502 CST: % Redundancy 
mode change to SSO

*Dec 16 04:20:43.502 CST: %VOICE_HA-7-STATUS: NONE->SSO; SSO mode will 
not take effect until after a platform 
reload.-->RF_STATUS_REDUNDANCY_MODE_CHANGE received *Dec 16 
04:20:44.220 CST: %SYS-5-CONFIG_I: Configured from memory by console 
*Dec 16 04:20:44.228 CST: %IOSXE_OIR-6-INSCARD: Card (rp) inserted in 
slot R1 *Dec 16 04:20:44.229 CST: %IOSXE_OIR-6-INSCARD: Card (fp) 
inserted in slot F0 *Dec 16 04:20:44.229 CST: %IOSXE_OIR-6-ONLINECARD: 
Card (fp) online in slot F0 *Dec 16 04:20:44.263 CST: 
%IOSXE_OIR-6-INSCARD: Card (fp) inserted in slot F1 *Dec 16 
04:20:44.263 CST: %IOSXE_OIR-6-INSCARD: Card (cc) inserted in slot 4 
*Dec 16 04:20:44.263 CST: %IOSXE_OIR-6-ONLINECARD: Card (cc) online in 
slot 4 *Dec 16 04:20:44.264 CST: %IOSXE_OIR-6-INSCARD: Card (cc) 
inserted in slot 5 *Dec 16 04:20:44.264 CST: %IOSXE_OIR-6-INSCARD: Card 
(cc) inserted in slot 6 *Dec 16 04:20:44.330 CST: %IOSXE_OIR-6-INSSPA: 
SPA inserted in subslot 4/1 *Dec 16 04:20:44.751 CST: %SYS-5-RESTART: 
System restarted -- Cisco IOS Software, IOS-XE Software 
(X86_64_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version
15.5(20141214:005145) [ece5_throttle_ios-ram-ece5-bk 105] Copyright (c) 
1986-2014 by Cisco Systems, Inc.
Compiled Sun 14-Dec-14 00:20 by ram
*Dec 16 04:20:44.775 CST: %XML-SRVC: Security Enforcement XML
Service(111) OK. PID=574
*Dec 16 04:20:44.775 CST: %SSH-5-ENABLED: SSH 1.99 has been enabled 
*Dec 16 04:20:45.453 CST: %LINK-3-UPDOWN: Interface GigabitEthernet0, 
changed state to up *Dec 16 04:20:45.543 CST: %LINK-5-CHANGED: 
Interface TenGigabitEthernet4/1/2, changed state to administratively 
down *Dec 16 04:20:45.546 CST: %LINK-5-CHANGED: Interface 
TenGigabitEthernet4/1/3, changed state to administratively down *Dec 16 
04:20:45.548 CST: %LINK-5-CHANGED: Interface TenGigabitEthernet4/1/4, 
changed state to administratively down *Dec 16 04:20:45.551 CST: 
%LINK-5-CHANGED: Interface TenGigabitEthernet4/1/5, changed state to 
administratively down *Dec 16 04:20:45.571 CST: %LINK-5-CHANGED: 
Interface TenGigabitEthernet4/1/6, changed state to administratively 
down *Dec 16 04:20:45.574 CST: %LINK-5-CHANGED: Interface 
TenGigabitEthernet4/1/7, changed state to administratively down *Dec 16 
04:20:45.576 CST: %LINK-5-CHANGED: Interface TenGigabitEthernet5/1/0, 
changed state to administratively down *Dec 16 04:20:45.578 CST: 
%LINK-5-CHANGED: Interface TenGigabitEthernet5/1/1, changed state to 
administratively down *Dec 16 04:20:45.580 CST: %LINK-5-CHANGED: 
Interface TenGigabitEthernet5/1/2, changed state to administratively 
down *Dec 16 04:20:45.582 CST: %LINK-5-CHANGED: Interface 
TenGigabitEthernet5/1/3, changed state to administratively down *Dec 16 
04:20:45.584 CST: %LINK-5-CHANGED: Interface TenGigabitEthernet5/1/4, 
changed state to administratively down *Dec 16 04:20:45.586 CST: 
%LINK-5-CHANGED: Interface TenGigabitEthernet5/1/5, changed state to 
administratively down *Dec 16 04:20:45.588 CST: %LINK-5-CHANGED: 
Interface TenGigabitEthernet5/1/6, changed state to administratively 
down *Dec 16 04:20:45.590 CST: %LINK-5-CHANGED: Interface 
TenGigabitEthernet5/1/7, changed state to administratively down *Dec 16 
04:20:45.596 CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/0:0, 
changed state to down *Dec 16 04:20:45.602 CST: %LINK-3-UPDOWN: 
Interface Integrated-Cable6/0/0:1, changed state to down *Dec 16 
04:20:45.603 CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/0:2, 
changed state to down *Dec 16 04:20:45.604 CST: %LINK-3-UPDOWN: 
Interface Integrated-Cable6/0/0:3, changed state to down *Dec 16 
04:20:45.606 CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/0:4, 
changed state to down *Dec 16 04:20:45.607 CST: %LINK-3-UPDOWN: 
Interface Integrated-Cable6/0/0:5, changed state to down *Dec 16 
04:20:45.608 CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/0:6, 
changed state to down *Dec 16 04:20:45.610 CST: %LINK-3-UPDOWN: 
Interface Integrated-Cable6/0/0:7, changed state to down *Dec 16 
04:20:45.648 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Bundle1, changed state to up *Dec 16 04:20:45.649 CST: %LINK-3-UPDOWN: 
Interface Bundle1, changed state to up *Dec 16 04:20:45.649 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/0, changed state to down *Dec 16 
04:20:45.649 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Cable6/0/0 changed state to down
*Dec 16 04:20:45.666 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:0, changed state to down *Dec 16 04:20:45.666 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:1, changed state to down 
*Dec 16 04:20:45.681 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:2, changed state to down *Dec 16 04:20:45.681 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:3, changed state to down 
*Dec 16 04:20:45.681 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:4, changed state to down *Dec 16 04:20:45.681 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:5, changed state to down 
*Dec 16 04:20:45.682 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:6, changed state to down *Dec 16 04:20:45.682 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:7, changed state to down 
*Dec 16 04:20:45.685 CST: %LINK-3-UPDOWN: Interface 
Integrated-Cable6/0/1:0, changed state to down *Dec 16 04:20:45.694 
CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/1:1, changed state 
to down *Dec 16 04:20:45.694 CST: %LINK-3-UPDOWN: Interface Cable6/0/1, 
changed state to down *Dec 16 04:20:45.694 CST: %SNMP-5-LINK_DOWN: 
LinkDown:Interface
Cable6/0/1 changed state to down
*Dec 16 04:20:45.699 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/1:0, changed state to down *Dec 16 04:20:45.703 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/1:1, changed state to down 
*Dec 16 04:20:45.706 CST: %LINK-3-UPDOWN: Interface 
Integrated-Cable6/0/1:2, changed state to down *Dec 16 04:20:45.707 
CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/1:3, changed state 
to down *Dec 16 04:20:45.709 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/2:0, changed state to down *Dec 16 04:20:46.469 CST: 
%SNMP-5-COLDSTART: SNMP agent on host sig-cbr is undergoing a cold 
start *Dec 16 04:20:46.472 CST: %LINEPROTO-5-UPDOWN: Line protocol on 
Interface GigabitEthernet0, changed state to up *Dec 16 04:20:46.543 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/2, changed state to down *Dec 16 04:20:46.546 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/3, changed state to down *Dec 16 04:20:46.548 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/4, changed state to down *Dec 16 04:20:46.551 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/5, changed state to down *Dec 16 04:20:46.571 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/6, changed state to down *Dec 16 04:20:46.574 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/7, changed state to down *Dec 16 04:20:46.576 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/0, changed state to down *Dec 16 04:20:46.578 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/1, changed state to down *Dec 16 04:20:46.580 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/2, changed state to down *Dec 16 04:20:46.582 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/3, changed state to down *Dec 16 04:20:46.584 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/4, changed state to down *Dec 16 04:20:46.586 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/5, changed state to down *Dec 16 04:20:46.588 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/6, changed state to down *Dec 16 04:20:46.590 
CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet5/1/7, changed state to down *Dec 16 04:20:46.641 
CST: %SYS-6-BOOTTIME: Time taken to reboot after reload =  374 seconds 
*Dec 16 04:20:53.697 CST: %IOSXE-1-PLATFORM: R0/0: kernel: Raptor MAC 
image download wrote 55917152 bytes *Dec 16 04:21:23.432 CST: 
%TRANSCEIVER-6-INSERTED: CLC4: iomd:
transceiver module inserted in TenGigabitEthernet4/1/0 *Dec 16 
04:21:23.435 CST: %TRANSCEIVER-6-INSERTED: CLC4: iomd:
transceiver module inserted in TenGigabitEthernet4/1/1 *Dec 16 
04:21:23.440 CST: %TRANSCEIVER-6-INSERTED: CLC4: iomd:
transceiver module inserted in TenGigabitEthernet4/1/4 *Dec 16 
04:21:29.430 CST: %CBRDTI-5-DTISLOT: DTI slot 4/1: card role changed to 
Active

*Dec 16 04:21:29.454 CST: %SPA_OIR-6-ONLINECARD: SPA (CBR-SUPPIC-8X10G) 
online in subslot 4/1 *Dec 16 04:21:31.403 CST: %LINK-3-UPDOWN: 
Interface TenGigabitEthernet4/1/0, changed state to up *Dec 16 
04:21:31.405 CST: %CBR_SPA-7-RAPTOR_ESI_EGRESS_HDR_LO_INTERRUPT:
CLC4: iomd:  LOCAL RAPTOR, DP 0, channel_not_found_err *Dec 16 
04:21:31.412 CST: %LINK-3-UPDOWN: Interface TenGigabitEthernet4/1/1, 
changed state to up *Dec 16 04:21:32.403 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface TenGigabitEthernet4/1/0, changed state to up *Dec 
16 04:21:32.412 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet4/1/1, changed state to up *Dec 16 04:21:41.171 CST: 
%IOSXE-3-PLATFORM: R0/0: kernel: i801_smbus
0000:00:1f.3: Transaction timeout
*Dec 16 04:21:41.174 CST: %IOSXE-3-PLATFORM: R0/0: kernel:
/nobackup/ram/ece5-bk/binos/os/linux/drivers/binos/i2c/max3674/max3674_
mai n.c:show_reg_pll (line 88): show_reg_pll failed *Dec 16 
04:21:58.237 CST: %IOSXE-5-PLATFORM: CLC6: cdman: Basestar FPGA rev_id 
0x00000002, fpga_rev_id 0x00000032 *Dec 16 04:21:59.074 CST: 
%CMRP-3-BAD_ID_HW: R0/0: cmand:  Failed Identification Test in CBR 
linecard. The module linecard slot 6 in this router may not be a 
genuine Cisco product. Cisco warranties and support programs only apply 
to genuine Cisco products. If Cisco determines that your insertion of 
non-Cisco memory, WIC cards, AIM cards,  Network Modules, SPA cards, 
GBICs or other modules into a  Cisco product is the cause of a support 
issue, Cisco may  deny support under your warranty or under a Cisco 
support  pro *Dec 16 04:21:59.075 CST: %IOSXE_OIR-6-ONLINECARD: Card 
(cc) online in slot 6 *Dec 16 04:22:08.825 CST: 
%ASR1000_INFRA-3-EOBC_SOCK: CLC6:
ubrclc-k9lc-ms:  Socket event for  EO6/0/1, fd 11, failed to bind; 
Address already in use success *Dec 16 04:22:09.605 CST:  SNMP IPC 
session up(RP <-> slot 6)!
*Dec 16 04:22:09.605 CST:  CMTS IPC session up!
*Dec 16 04:22:14.564 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Cable6/0/0-upstream0 changed state to up *Dec 16 04:22:14.565 CST: 
%SNMP-5-LINK_UP: LinkUp:Interface
Cable6/0/0-upstream1 changed state to up *Dec 16 04:22:14.566 CST: 
%SNMP-5-LINK_UP: LinkUp:Interface
Cable6/0/2-upstream0 changed state to up *Dec 16 04:22:14.566 CST: 
%SNMP-5-LINK_UP: LinkUp:Interface
Cable6/0/2-upstream1 changed state to up *Dec 16 04:22:15.051 CST: 
%SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/0 changed state to up *Dec 
16 04:22:15.258 CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/1 
changed state to up *Dec 16 04:22:15.258 CST: %SNMP-5-LINK_UP: 
LinkUp:Interface Cable6/0/2 changed state to up *Dec 16 04:22:15.259 
CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/3 changed state to up 
*Dec 16 04:22:15.259 CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/4 
changed state to up *Dec 16 04:22:15.411 CST: %SNMP-5-LINK_UP: 
LinkUp:Interface Cable6/0/5 changed state to up *Dec 16 04:22:15.411 
CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/6 changed state to up 
*Dec 16 04:22:15.411 CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/7 
changed state to up *Dec 16 04:22:15.411 CST: %SNMP-5-LINK_UP: 
LinkUp:Interface Cable6/0/8 changed state to up *Dec 16 04:22:15.432 
CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/9 changed state to up 
*Dec 16 04:22:15.432 CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/10 
changed state to up *Dec 16 04:22:15.433 CST: %SNMP-5-LINK_UP: 
LinkUp:Interface Cable6/0/11 changed state to up *Dec 16 04:22:15.433 
CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/12 changed state to up 
*Dec 16 04:22:15.433 CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/13 
changed state to up *Dec 16 04:22:15.433 CST: %SNMP-5-LINK_UP: 
LinkUp:Interface Cable6/0/14 changed state to up *Dec 16 04:22:15.433 
CST: %SNMP-5-LINK_UP: LinkUp:Interface Cable6/0/15 changed state to up 
*Dec 16 04:22:15.677 CST: %LINEPROTO-5-UPDOWN: Line protocol on 
Interface Cable6/0/8, changed state to up *Dec 16 04:22:15.678 CST: 
%LINEPROTO-5-UPDOWN: Line protocol on Interface Cable6/0/9, changed 
state to up *Dec 16 04:22:15.901 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface Cable6/0/10, changed state to up *Dec 16 
04:22:15.902 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/11, changed state to up *Dec 16 04:22:15.902 CST: 
%LINEPROTO-5-UPDOWN: Line protocol on Interface Cable6/0/12, changed 
state to up *Dec 16 04:22:15.903 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface Cable6/0/13, changed state to up *Dec 16 
04:22:15.903 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/14, changed state to up *Dec 16 04:22:15.904 CST: 
%LINEPROTO-5-UPDOWN: Line protocol on Interface Cable6/0/15, changed 
state to up *Dec 16 04:22:17.046 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface Cable6/0/0, changed state to up *Dec 16 
04:22:17.047 CST: %LINK-3-UPDOWN: Interface Cable6/0/0, changed state 
to up *Dec 16 04:22:17.256 CST: %LINEPROTO-5-UPDOWN: Line protocol on 
Interface Cable6/0/1, changed state to up *Dec 16 04:22:17.257 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/1, changed state to up *Dec 16 
04:22:17.259 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/2, changed state to up *Dec 16 04:22:17.260 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/2, changed state to up *Dec 16 
04:22:17.260 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/3, changed state to up *Dec 16 04:22:17.260 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/3, changed state to up *Dec 16 
04:22:17.260 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/4, changed state to up *Dec 16 04:22:17.260 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/4, changed state to up *Dec 16 
04:22:17.411 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/5, changed state to up *Dec 16 04:22:17.411 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/5, changed state to up *Dec 16 
04:22:17.411 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/6, changed state to up *Dec 16 04:22:17.411 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/6, changed state to up *Dec 16 
04:22:17.411 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Cable6/0/7, changed state to up *Dec 16 04:22:17.412 CST: 
%LINK-3-UPDOWN: Interface Cable6/0/7, changed state to up *Dec 16 
04:22:16.714 CST: %IOSXE-5-PLATFORM: CLC6: cdman: DS-JIB:ILK Interrupts 
Enabled. (Init:20539, Check:9566 1stPKO:8942) *Dec 16 04:22:17.809 CST: 
%CMRP-3-IDPROM_SENSOR: R0/0: cmand:  One or more sensor fields from the 
idprom failed to parse properly because Invalid argument.
Dec 16 04:22:57.161 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream0 changed state to down Dec 16 
04:22:57.161 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream1 changed state to down Dec 16 
04:22:57.161 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream2 changed state to down Dec 16 
04:22:57.162 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream3 changed state to down Dec 16 
04:22:57.162 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream4 changed state to down Dec 16 
04:22:57.162 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream5 changed state to down Dec 16 
04:22:57.162 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream6 changed state to down Dec 16 
04:22:57.162 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream7 changed state to down Dec 16 
04:22:57.163 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream8 changed state to down Dec 16 
04:22:57.163 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream9 changed state to down Dec 16 
04:22:57.163 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/0-downstream10 changed state to down Dec 16 
04:22:57.163 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream0 changed state to down Dec 16 
04:22:57.164 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream1 changed state to down Dec 16 
04:22:57.164 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream2 changed state to down Dec 16 
04:22:57.164 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream3 changed state to down Dec 16 
04:22:57.164 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream4 changed state to down Dec 16 
04:22:57.164 CST: %SNMP-5-LINK_DOWN: LinkDown:Interface
Integrated-Cable6/0/1-downstream5 changed state to down Dec 16 
04:22:57.183 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream0 changed state to up Dec 16 
04:22:57.184 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream1 changed state to up Dec 16 
04:22:57.189 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream2 changed state to up Dec 16 
04:22:57.211 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream3 changed state to up Dec 16 
04:22:57.212 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream4 changed state to up Dec 16 
04:22:57.212 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream6 changed state to up Dec 16 
04:22:57.213 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream7 changed state to up Dec 16 
04:22:57.213 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream8 changed state to up Dec 16 
04:22:57.213 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream9 changed state to up Dec 16 
04:22:57.213 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/0-downstream10 changed state to up Dec 16 
04:22:57.214 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream0 changed state to up Dec 16 
04:22:57.424 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream1 changed state to up Dec 16 
04:22:57.426 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream2 changed state to up Dec 16 
04:22:57.435 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream3 changed state to up Dec 16 
04:22:57.437 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream4 changed state to up Dec 16 
04:22:57.449 CST: %SNMP-5-LINK_UP: LinkUp:Interface
Integrated-Cable6/0/1-downstream5 changed state to up Dec 16 
04:22:59.219 CST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Integrated-Cable6/0/1:0, changed state to up Dec 16 04:22:59.219 CST: 
%LINK-3-UPDOWN: Interface Integrated-Cable6/0/1:0, changed state to up 
Dec 16 04:22:59.427 CST: %LINEPROTO-5-UPDOWN: Line protocol on 
Interface Integrated-Cable6/0/1:1, changed state to up Dec 16 
04:22:59.427 CST: %LINK-3-UPDOWN: Interface Integrated-Cable6/0/1:1, 
changed state to up Dec 16 04:22:59.449 CST: %LINEPROTO-5-UPDOWN: Line 
protocol on Interface Wideband-Cable6/0/0:0, changed state to up Dec 16 
04:22:59.450 CST: %LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:0, 
changed state to up Dec 16 04:22:59.450 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:1, changed state to up Dec 16 04:22:59.450 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:2, changed state to up 
Dec 16 04:22:59.450 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:3, changed state to up Dec 16 04:22:59.450 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:4, changed state to up 
Dec 16 04:22:59.450 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:5, changed state to up Dec 16 04:22:59.451 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/0:6, changed state to up 
Dec 16 04:22:59.451 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/0:7, changed state to up Dec 16 04:22:59.451 CST: 
%LINEPROTO-5-UPDOWN: Line protocol on Interface Wideband-Cable6/0/1:0, 
changed state to up Dec 16 04:22:59.451 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/1:0, changed state to up Dec 16 04:22:59.451 CST: 
%LINEPROTO-5-UPDOWN: Line protocol on Interface Wideband-Cable6/0/1:1, 
changed state to up Dec 16 04:22:59.452 CST: %LINK-3-UPDOWN: Interface 
Wideband-Cable6/0/1:1, changed state to up Dec 16 04:22:59.452 CST: 
%LINK-3-UPDOWN: Interface Wideband-Cable6/0/2:0, changed state to up 
Dec 16 04:23:27.352 CST: %IOSXE-5-PLATFORM: CLC6: cdman: DSPHY Gemini 
module  1 was not present Dec 16 04:26:59.885 CST: 
%ENVIRONMENTAL-1-ALERT: Temp: INLET, Location:
6, State: Critical, Reading: 53 Celsius sig-cbr#]]></aml-block:Data> 
</aml-block:Attachment> </aml-block:Attachments> </aml-block:Block> 
</soap-env:Body> </soap-env:Envelope>

Additional References

Related Documents

Related Topic Document Title

Smart Call Home site page on Cisco.com for access to all related product information.

Cisco Smart Call Home site

The User Guide explains how the Smart Call Home service offers web-based access to important information on select Cisco devices. The User Guide also describes the higher network availability and increased operational efficiency by providing real-time alerts.

Smart Call Home User Guide

Call Home Quick Start Guide

Smart Call Home Quick Start Configuration Guide for Cisco cBR Series Routers

MIBs

MIB MIBs Link
CISCO-CALLHOME-MIB

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

Technical Assistance

Description Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

You can subscribe to various services to receive security and technical information about your products. The services include the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/support

Feature Information for Call Home

Use Cisco Feature Navigator to find information about the platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to the www.cisco.com/go/cfn link. An account on the Cisco.com page is not required.


Note

The following table lists the software release in which a given feature is introduced. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 11. Feature Information for Call Home

Feature Name

Releases

Feature Information

Smart Call Home

Cisco IOS XE Everest 16.6.1

This feature was integrated into Cisco IOS XE Everest 16.6.1 on theCisco cBR Series Converged Broadband Routers.