Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
Configuring Call Home
Downloads: This chapterpdf (PDF - 910.0KB) The complete bookPDF (PDF - 7.89MB) | Feedback

Table of Contents

Configuring Call Home

Contents

Information About Call Home

Benefits of Using Call Home

How to Obtain Smart Call Home Service

Prerequisites for Call Home

How to Configure Call Home

Configuring the Management Interface VRF

What To Do Next

Configuring a Destination Profile

Configuring a Destination Profile to Send Email Messages

Configuring a Destination Profile to Send HTTP Messages

Working With Destination Profiles

Subscribing to Alert Groups

Periodic Notification

Message Severity Threshold

Syslog Pattern Matching

Configuring Contact Information

Example

Configuring the Number of Call Home Messages Sent Per Minute

Enabling and Disabling Call Home

Sending Call Home Communications Manually

Sending a Call Home Test Message Manually

Sending Call Home Alert Group Messages Manually

Submitting Call Home Analysis and Report Requests

Sending the Output of a Command to Cisco or an E-Mail Address

How To Configure Call Home to Support the Smart Call Home Service

Prerequisites

Configure and Enable Call Home

Declare and Authenticate a CA Trustpoint

Examples

Start Smart Call Home Registration

What To Do Next

Displaying Call Home Configuration Information

Examples

Default Settings

Alert Group Trigger Events and Commands

Message Contents

Sample Syslog Alert Notification in Long Text Format

Sample Syslog Alert Notification in XML Format

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for Call Home

Configuring Call Home

Revised: November 21, 2013

The Call Home feature provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, e-mail notification to a Network Operations Center, XML delivery to a support website, and utilization of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC). This document describes how to configure the Call Home feature on Cisco ASR 1000 Series Aggregation Services Routers beginning with Cisco IOS XE Release 2.6.

Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the “Feature Information for Call Home” section.

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn . An account on Cisco.com is not required.

Information About Call Home

Call Home provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, e-mail notification to a Network Operations Center, XML delivery to a support website, and utilization 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, diagnostics, environmental conditions, inventory, and syslog 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 the Cisco TAC (depending 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.

This section contains the following topics:

Benefits of Using Call Home

The Call Home feature offers the following benefits:

  • Multiple message-format options:

Short Text—Suitable for pagers or printed reports.

Plain Text—Full formatted message information suitable for human reading.

XML—Matching readable format using Extensible Markup Language (XML) and Adaptive Markup Language (AML) document type definitions (DTDs). The XML format enables communication with the Cisco Smart Call Home server.

  • Multiple concurrent message destinations.
  • Multiple message categories, including configuration, diagnostics, environmental conditions, inventory, and syslog events.
  • Filtering of messages by severity and pattern matching.
  • Scheduling of periodic message sending.

How to Obtain Smart Call Home Service

If you have a service contract directly with Cisco Systems, you can register your Call Home devices for the Cisco Smart Call Home service. Smart Call Home provides fast resolution of system problems by analyzing Call Home messages sent from your devices and providing background information and recommendations. For issues that can be identified as known, automatic Service Requests can be generated with the Cisco TAC. This depends on the Smart Call Home service support in place for your device and the severity of the alert.

Smart Call Home offers the following features:

  • Analysis of Call Home messages from your device, and where supported, automatic Service Request generation routed to the appropriate TAC team, including detailed diagnostic information to speed problem resolution.
  • Continuous device health monitoring.
  • Analysis of Call Home messages from your device.
  • Secure message transport directly from your device or through a downloadable Transport Gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices may not be connected directly to the Internet.
  • Web-based access to Call Home messages and recommendations, inventory, and configuration information for all Call Home devices. Provides access to associated Field Notices, Security Advisories, and End-of-Life Information.

You need the following items to register:

  • SMARTnet contract number for your router.
  • Your e-mail address
  • Your Cisco.com ID

For information about how to configure Call Home to work with the Smart Call Home service, see the “How To Configure Call Home to Support the Smart Call Home Service” section.

For detailed information on Smart Call Home, see the Smart Call Home page at:

http://www.cisco.com/en/US/products/ps7334/serv_home.html

Prerequisites for Call Home

How you configure Call Home depends on how you intend to use the feature. Consider the following requirements before you configure Call Home:

  • Obtain e-mail, phone, and street address information for the Call Home contact to be configured so that the receiver can determine the origin of messages received.
  • Identify the name or IPv4 address of a primary Simple Mail Transfer Protocol (SMTP) server and any backup servers, if using e-mail message delivery.
  • Configure a trustpoint certificate authority (CA) if using secure HTTP (HTTPS) message delivery. For example, this procedure is required if you are using the HTTPS server for Cisco Smart Call Home Service in the CiscoTAC-1 profile for Call Home.
  • Verify IP connectivity from the router to the e-mail server(s) or the destination HTTP server.
  • If Cisco Smart Call Home is used, verify an active service contract exists for the device being configured.

How to Configure Call Home

To configure Call Home, complete the following tasks:

Configuring the Management Interface VRF

The Call Home feature on the Cisco ASR 1000 Series Routers requires use of the Gigabit Ethernet Management interface virtual routing and forwarding (VRF) instance. The Gigabit Ethernet Management interface is automatically part of its own VRF named “Mgmt-intf.”

To configure the Management interface VRF, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. interface GigabitEthernet 0

3. vrf forwarding Mgmt-intf

4. ip address ip-address mask [ secondary [ vrf vrf-name ]]

or

ipv6 address { X:X:X:X::X link-local | X:X:X:X::X / prefix [ anycast | eui-64 ] | autoconfig [ default ]}

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

interface GigabitEthernet 0

 

Router(config)# interface GigabitEthernet0

(Required) Specifies the Gigabit Ethernet Management interface on the Cisco ASR 1000 Series Router.

Step 3

vrf forwarding Mgmt-intf

 

Router(config-if)# vrf forwarding Mgmt-intf

(Required) Associates the Mgmt-intf VRF with the Gigabit Ethernet Management interface. This command is configured by default.

Step 4

ip address ip-address mask [ secondary [ vrf vrf-name ]]

 

or

ipv6 address { X:X:X:X::X link-local | X:X:X:X::X / prefix [ anycast | eui-64 ] | autoconfig [ default ]}

 

Router(config-if)# ip address 10.10.10.10 0.0.0.0

(Required) Specifies the IPv4 or IPv6 addressing for the interface.

What To Do Next

To find out more about the Gigabit Ethernet Management interface on the Cisco ASR 1000 Series Routers or perform additional related configuration tasks on the management interface, see the “$paratext>” section .

Configuring a Destination Profile

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

You can create and define a new destination profile or copy and use another destination profile. If you define a new destination profile, you must assign a profile name.


Note The Call Home feature provides a predefined profile named CiscoTAC-1 that is inactive by default. The CiscoTAC-1 profile is intended for use with the Smart Call Home service, which requires certain additional configuration steps to enable the service with the Call Home feature. For more information about this profile, see the “Using the Predefined CiscoTAC-1 Destination Profile” section.


You can configure the following attributes for a destination profile:

  • Profile name—A 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—The transport mechanism, either e-mail or HTTP (including HTTPS), for delivery of alerts.

For user-defined destination profiles, e-mail is the default, and you can enable one or both transport mechanisms. If you disable both methods, e-mail is enabled.

For the predefined Cisco TAC profile, you can enable either transport mechanism, but not both.

  • Destination address—The actual address related to the transport method to which the alert should be sent.
  • 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 Cisco TAC profile, only XML is allowed. If you use the Cisco Smart Call Home service, the destination profile must use the XML message format.
  • Message size—The maximum destination message size. The valid range is 50 to 3,145,728 bytes and the default is 3,145,728 bytes.

This section includes the following tasks:

Configuring a Destination Profile to Send Email Messages

To configure Call Home to send email messages, complete the following tasks:

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.

SUMMARY STEPS

1. configure terminal

2. call-home

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

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

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

 

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

Specifies an e-mail server and its relative priority among configured e-mail servers, where:

  • ipv4-address —Specifies the IPv4 address of the mail server.
  • name —Specifies the mail server’s fully qualified domain name (FQDN) of 64 characters or less.
  • number —Assigns a number between 1 (highest priority) and 100 (lowest priority).

Example:

The following example shows the configuration of a primary mail server (named “smtp.example.com”) and secondary mail server at IP address 192.168.0.1:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.

Router(config)# call-home

Router(cfg-call-home)# mail-server smtp.example.com priority 1

Router(cfg-call-home)# mail-server 192.168.0.1 priority 2

Router(cfg-call-home)# exit

Router(config)#

Associating the Management Interface VRF With Call Home

The Call Home feature requires the management interface VRF (Mgmt-intf) to provide e-mail messaging support. If you have not configured the management interface VRF, see the “Configuring the Management Interface VRF” section.

To associate the management interface VRF with Call Home, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. vrf Mgmt-intf

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

vrf Mgmt-intf

 

Router(cfg-call-home)# vrf Mgmt-intf

(Required) Associates the Mgmt-intf VRF for the email transport method using Call Home.

Configuring a Destination Profile for E-mail

To configure a destination profile for e-mail transport, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. profile name

4. destination transport-method email

5. destination address email email-address

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

7. destination message-size bytes

8. active

9. exit

10. end

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call - home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

profile name

 

Router(config-call-home)# profile profile1

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

Step 4

destination transport-method email

 

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

(Optional) Configures the message transport method for email. This is the default.

Step 5

destination address email email-address

 

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

(Required) Configures the destination e-mail address to which Call Home messages are sent.

Step 6

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

 

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

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

Step 7

destination message-size bytes

 

Router(cfg-call-home-profile)# destination message-size 3145728

(Optional) Configures a maximum destination message size (from 50 to 3145728 bytes) for the destination profile. The default is 3145728 bytes.

Step 8

active

 

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

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

Step 9

exit

 

Router(cfg-call-home-profile)# exit

Exits call home destination profile configuration mode and returns to call home configuration mode.

Step 10

end

 

Router(cfg-call-home)# end

Returns to privileged EXEC mode.

Configuring Other Email Options

For the e-mail transport method, you can also configure the from and reply-to e-mail addresses by completing the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. sender from email-address

4. sender reply-to email-address

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

sender from email-address

 

Router(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 4

sender reply-to email-address

 

Router(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.

Configuring a Destination Profile to Send HTTP Messages

To configure Call Home to send HTTP (or HTTPS) messages, complete the following tasks:

Configuring the HTTP Source Interface

If you are using HTTP or HTTPS to send Call Home messages, then you must configure the VRF management interface as the HTTP client source interface.

SUMMARY STEPS

1. configure terminal

2. ip http client source-interface type number

3. end

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

ip http client source-interface type number

 

Router(config)# ip http client source-interface gigabitethernet 0

Configures the source interface for the HTTP client.

Note On the Cisco ASR 1000 Series Router, this interface should be the VRF management interface.

Step 3

end

 

Router(cfg-call-home)# end

Returns to privileged EXEC mode.

Configuring a Destination Profile for HTTP

To configure a destination profile for http transport, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. profile name

4. destination transport-method http

5. destination address http url

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

7. destination message-size bytes

8. active

9. exit

10. end

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call - home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

profile name

 

Router(config-call-home)# profile test

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

Step 4

destination transport-method http

 

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

Enables the HTTP message transport method.

Step 5

destination address http url

 

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

Configures the destination 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 trustpoint CA.

Step 6

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

 

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

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

Step 7

destination message-size bytes

 

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

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

Step 8

active

 

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

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

Step 9

exit

 

Router(cfg-call-home-profile)# exit

Exits call home destination profile configuration mode and returns to call home configuration mode.

Step 10

end

 

Router(cfg-call-home)# end

Returns to privileged EXEC mode.

Configuring a Trustpoint Certificate Authority

If you are using the HTTP transport method and specifying an HTTPS destination URL, then you will also need to configure a trustpoint certificate authority (CA).

For more information about how to configure a trustpoint CA, see the “Declare and Authenticate a CA Trustpoint” section. That section describes how to configure a CA trustpoint for a secure Cisco server to use with the Smart Call Home service, but can be applied to other secure server configuration as needed by your site using the required certificate for your secure server.

Working With Destination Profiles

This section describes some of the tasks that you can complete with destination profiles:

Activating and Deactivating a Destination Profile

Except for the predefined CiscoTAC-1 profile, all Call Home destination profiles are automatically activated once you create them. If you do not want to use a profile right way, you can deactivate the profile. The CiscoTAC-1 profile is inactive by default and must be activated to be used.

To activate or deactivate a destination profile, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. profile name

4. active

5. no active

6. end

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call - home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

profile name

 

Router(config-call-home)# profile test

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

Step 4

active

 

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

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

Step 5

no active

 

Router(cfg-call-home-profile)# no active

Disables the destination profile.

Step 6

end

 

Router(cfg-call-home)# end

Exits call home destination profile configuration mode and returns to privileged EXEC mode.

Copying a Destination Profile

To create a new destination profile by copying an existing profile, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. copy profile source-profile target-profile

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

copy profile source-profile target-profile

 

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

Creates a new destination profile with the same configuration settings as the existing destination profile, where:

  • source-profile —Specifies the existing name of the profile.
  • target-profile —Specifies a name for the new copy of the profile.

Renaming a Destination Profile

To change the name of an existing profile, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. rename profile source-profile target-profile

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

rename profile source-profile target-profile

 

Router(cfg-call-home)# rename profile2 testprofile

Renames an existing source file, where:

  • source-profile —Specifies the existing name of the profile.
  • target-profile —Specifies a new name for the existing profile.

Using the Predefined CiscoTAC-1 Destination Profile

The CiscoTAC-1 profile is automatically configured in the Call Home feature for your use with the Cisco Smart Call Home service. This profile includes certain information, such as the destination e-mail address and HTTPS URL, and default alert groups for communication with the Smart Call Home service. Some of these attributes, such as the destination e-mail address, HTTPS URL, and message format cannot be modified.

You can use either email or http transport to communicate with the Smart Call Home service backend server. By default, the CiscoTAC-1 profile is inactive and uses email as the default transport method. To use email transport, you only need to enable the profile. However, to use this profile with the Cisco Smart Call Home service secure server (via HTTPS), you not only must enable the profile, but you must also change the transport method to HTTP as shown in the following example:

Router# configure terminal
Router(config)# call-home
Router(config-call-home)# profile CiscoTAC-1
Router(cfg-call-home-profile)# destination transport-method http
Router(cfg-call-home-profile)# active
 

For more information about additional requirements for Configuring the Smart Call Home service, see the “How To Configure Call Home to Support the Smart Call Home Service” section.

Verifying the Call Home Profile Configuration

To verify the profile configuration for Call Home, use the show call-home profile command. See the “Displaying Call Home Configuration Information” section for more information and examples.

Subscribing to Alert Groups

An alert group is a predefined subset of Call Home alerts supported in all routers. Different types of Call Home alerts are grouped into different alert groups depending on their type. The following alert groups are available on the Cisco ASR 1000 Series Routers:

  • Configuration
  • Diagnostic
  • Environment
  • Inventory
  • Syslog

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

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


Note A Call Home alert is only sent to destination profiles that have subscribed to the alert group containing that Call Home alert. In addition, the alert group must be enabled.


Periodic Notification

When you subscribe a destination profile to either the Configuration or the Inventory alert group, you can choose to receive the alert group messages asynchronously or periodically at a specified time. The sending period can be one of the following:

  • 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.

Message Severity Threshold

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


Note When syslog level is changed via IOS CLI, the new value is propagated to non-IOS processes as well, with the result that these processes no longer send syslog messages of lower priority to IOS to process, thus "saving" CPU cycles for IOS


Table 9-1 lists the keywords used to configure the severity, which range from catastrophic (level 9, highest level of urgency) to debugging (level 0, lowest level of urgency). If no severity threshold is configured, the default is debugging (level 0). However, the default is not recommended due to the number of messages that will be triggered.


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


 

Table 9-1 Severity and Syslog Level Mapping

Level
Keyword
Syslog Level
Description

9

catastrophic

N/A

Network-wide catastrophic failure.

8

disaster

N/A

Significant network impact.

7

fatal

Emergency (0)

System is unusable.

6

critical

Alert (1)

Critical conditions, immediate attention 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 is sent only if it contains the specified pattern and meets the severity threshold. If the pattern contains spaces, you must enclose it within double quotation marks(“ ”) when configuring it. You can specify up to five patterns for each destination profile.

To subscribe a destination profile to one or more alert groups, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. alert-group { all | configuration | environment | inventory | syslog }

4. profile name

5. subscribe-to-alert-group all

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

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

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

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

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

11. exit

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

alert-group { all | configuration | environment | inventory | syslog }

 

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

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

Step 4

profile name

 

Router(cfg-call-home)# profile profile1

Enters call home destination profile configuration mode for the specified destination profile.

Step 5

subscribe-to-alert-group all

 

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

(Optional) Subscribes this destination profile to all available alert groups.

Note Alternatively, you can also subscribe to alert groups individually by specific type as described in steps 6 through 9.

Step 6

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

 

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

Subscribes this destination profile to the Configuration alert group, with an optional periodic value.

Step 7

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

 

Router(cfg-call-home-profile)# subscribe-to-alert-group diagnostic severity critical

Subscribes this destination profile to the Diagnostic alert group, with an optional severity level.

Step 8

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

 

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

Subscribes this destination profile to the Environment alert group, with an optional severity level.

Step 9

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

 

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

Subscribes this destination profile to the Inventory alert group, with an optional periodic value.

Step 10

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

 

Router(cfg-call-home-profile)# subscribe-to-alert-group syslog

Subscribes this destination profile to the Syslog alert group, with an optional severity level. You can specify a pattern to be matched in the syslog message, up to a maximum of five patterns per profile. If the pattern contains spaces, you must enclose it within double quotation marks (“ ”).

Step 11

exit

 

Router(cfg-call-home-profile)# exit

Exits call home destination profile configuration mode.

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:

SUMMARY STEPS

1. configure terminal

2. call-home

3. contact-email-addr email-addres s

4. phone-number + phone-number

5. street-address street-address

6. customer-id text

7. site-id text

8. contract-id text

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router> configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

contact-email-addr email-address

 

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

 

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

 

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

 

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

 

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

 

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 (“ ”).

Example

The following example shows the configuration of contact information:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.

Router(config)# call-home

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

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

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

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

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

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

Router(cfg-call-home)# exit

Configuring the Number of Call Home Messages Sent Per Minute

The Call Home feature defaults to a maximum of 20 messages per minute. If you want to change that value, complete the following steps:

SUMMARY STEPS

1. configure terminal

2. call-home

3. rate-limit number

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call-home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

rate-limit number

 

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

Specifies a limit on the number of messages sent per minute. Range 1 to 60. The default is 20.

Enabling and Disabling Call Home

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

SUMMARY STEPS

1. configure terminal

2. service call-home

3. no service call-home

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

service call-home

 

Router(config)# service call-home

Enables the Call Home feature.

Step 3

no service call-home

 

Router(config)# no service call-home

Disables the Call Home feature.

Sending Call Home Communications Manually

You can manually send several types of Call Home communications. To send Call Home communications, complete the tasks in this section. This section contains the following subsections:

Sending a Call Home Test Message Manually

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

SUMMARY STEPS

1. call-home test [ test-message ] profile name

DETAILED STEPS

Command or Action
Purpose

Step 1

call-home test [ test-message ] profile name

 

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

You can use the call-home send command to manually send a specific alert group message.

Note the following guidelines when manually sending a Call Home alert group message:

  • Configuration, diagnostic, and inventory alert groups can be sent manually.
  • When you manually trigger an alert group message and you specify a destination profile name, a message is sent to the destination profile regardless of the active status, subscription status, or severity setting of the profile.
  • When you manually trigger a 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.
  • When you manually trigger a diagnostic alert group message and do not specify a destination profile name, a message is sent to all active profiles that have a lower severity subscription than the severity of the diagnostic results of the specified slot.

To manually trigger Call Home alert group messages, complete the following steps:

SUMMARY STEPS

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

2. call-home send alert-group diagnostic slot R0 [ profile name ]

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

DETAILED STEPS

Command or Action
Purpose

Step 1

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

 

Router# call-home send alert-group configuration profile CiscoTAC-1

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

Step 2

call-home send alert-group diagnostic slot R0 [ profile name ]

 

Router# call-home send alert-group diagnostic slot R0 profile CiscoTAC-1

Sends a diagnostic alert group message to one destination profile if specified, or to all subscribed destination profiles with a lower severity subscription than the diagnostic result for route processor slot 0.

Step 3

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

 

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:

SUMMARY STEPS

1. call-home request output-analysis “ show-command [ profile name ] [ ccoid user-id ]

2. call-home request { config-sanity | bugs-list | command-reference | product-advisory } [ profile name ] [ ccoid user-id ]

DETAILED STEPS

Command or Action
Purpose

Step 1

call-home request output-analysis show-command

[ profile name ] [ ccoid user-id ]

 

Router# 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 }

[ profile name ] [ ccoid user-id ]

 

 

Router# 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.

Example

The following example shows a request for analysis of a user-specified show command:

Router# call-home request output-analysis "show diag" profile TG

Sending the Output of a Command to Cisco or an E-Mail Address

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 CLI command can be any run command, including commands for all modules. The command must be contained in quotes (“”).
  • If an e-mail address is specified, the command output is sent to that address. If no e-mail address is specified, the output is sent to the Cisco TAC (attach@cisco.com). The e-mail is sent in long text format with the service number, if specified, in the subject line.
  • The service number is required only if no e-mail address is specified, or if a Cisco TAC e-mail address is specified.

To execute a CLI command and e-mail the command output, complete the following step:

SUMMARY STEPS

1. call-home send “ command { email email-addr [ tac-service-request request-number ] | tac-service-request request-number email email-addr }

DETAILED STEPS

Command or Action
Purpose

Step 1

call-home send command

{ email email-addr [ tac-service-request request-number ] | tac-service-request request-number [ email email-addr ]}

 

Router# call-home send “show call-home” email support@example.com

Executes the specified CLI command and e-mails the output, where:

  • email email-addr —Specifies the email address to which the command output should be sent. This keyword is optional if used after entering the tac-service-request option.
  • tac-service-request request-number —Specifies the TAC service request number that will appear in the subject line of the email. This keyword is optional if used after entering the email option.

Example

The following example shows how to send the output of a CLI command to a user-specified e-mail address:

Router# call-home send "show diag" email support@example.com

How To Configure Call Home to Support the Smart Call Home Service

.

This section provides an overview of the minimum steps required to configure the Call Home feature on a Cisco device, and other required supporting configuration to communicate securely with the Smart Call Home service using HTTPS:

Prerequisites

Before you configure and use the Smart Call Home Service, be sure that you have completed the following prerequisites:

  • Verify that you have an active Cisco Systems service contract for the device being configured.
  • Verify that you have IP connectivity to the Cisco HTTPS server.
  • Obtain the latest Cisco Systems server security certificate.

Configure and Enable Call Home

To establish the Cisco Smart Call Home service, there are certain steps that must be peformed to configure and enable the Call Home feature on the Cisco ASR 1000 Series Router.

The CiscoTAC-1 profile is predefined in the Call Home feature to communicate using email to the backend server for the Smart Call Home service. The URL to the Cisco HTTPS backend server is also predefined. This profile is inactive by default.

However, unlike other profiles that you can configure in Call Home to support both transport methods, the CiscoTAC-1 profile can only use one transport method at a time. Therefore, to use this profile with the Cisco Smart Call Home HTTPS server, you must change the transport method from email to HTTP and enable the profile. In addition, you must minimally specify a contact e-mail address and enable the Call Home feature.

SUMMARY STEPS

1. configure terminal

2. call-home

3. profile CiscoTAC-1

4. destination transport-method http

5. active

6. exit

7. contact-email-addr email-address

8. exit

9. service call-home

10. exit

11. copy running-config startup-config

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

call - home

 

Router(config)# call-home

Enters call home configuration mode.

Step 3

profile CiscoTAC-1

 

Router(config-call-home)# profile CiscoTAC-1

Enters call home destination profile configuration mode for the CiscoTAC-1 destination profile.

Step 4

destination transport-method http

 

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

(Required only if using HTTPS) Configures the message transport method for http.

Step 5

active

 

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

Enables the destination profile.

Step 6

exit

 

Router(cfg-call-home-profile)# exit

Exits call home destination profile configuration mode and returns to call home configuration mode.

Step 7

contact-email-addr email-address

 

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 8

exit

 

Router(cfg-call-home)# exit

Exits call home configuration mode and returns to global configuration mode.

Step 9

service call-home

 

Router(config)# service call-home

Enables the Call Home feature.

Step 10

exit

 

Router(config)# exit

Exits global configuration mode and returns to privileged EXEC mode.

Step 11

copy running-config startup-config

 

Router# copy running-config startup-config

Saves the configuration to NVRAM.

Declare and Authenticate a CA Trustpoint

To establish communication with the Cisco HTTPS server for Smart Call Home service, you must declare and authenticate the Cisco server security certificate.

SUMMARY STEPS

1. configure terminal

2. crypto pki trustpoint name

3. enrollment terminal

4. exit

5. crypto pki authenticate name

6. At the prompt, paste the security certificate text.

7. quit

8. yes

9. end

10. copy running-config startup-config

DETAILED STEPS

Command or Action
Purpose

Step 1

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 2

crypto pki trustpoint name

 

Router(config)# crypto pki trustpoint cisco

Declares a CA trustpoint on your router and enters CA trustpoint configuration mode.

Step 3

enrollment terminal

 

Router(ca-trustpoint)# enrollment terminal

Specifies a manual cut-and-paste method of certificate enrollment.

Step 4

exit

 

Router(ca-trustpoint)# exit

Exits CA trustpoint configuration mode and returns to global configuration mode.

Step 5

crypto pki authenticate name

 

Router(config)# crypto pki authenticate cisco

Authenticates the named CA.

Note The CA name should match the name specified in the crypto pki trustpoint command.

Step 6

At the prompt, paste the security certificate text.

 

Enter the base 64 encoded CA certificate.

End with a blank line or the word "quit" on a line by itself

<Paste certificate text here>

Specifies the security certificate text.

Step 7

quit

 

quit

Specifies the end of the security certificate text.

Step 8

yes

 
% Do you accept this certificate? [yes/no]: yes

Confirms acceptance of the entered security certificate.

Step 9

end

 

Router# end

Exits global configuration mode and returns to privileged EXEC mode.

Step 10

copy running-config startup-config

 

Router# copy running-config startup-config

Saves the configuration to NVRAM.

Examples

This example shows how to declare and authenticate the Cisco server security certificate and establish communication with the Cisco HTTPS server for Smart Call Home service:

Router# configure terminal
Router(config)# crypto pki trustpoint cisco
Router(ca-trustpoint)# enrollment terminal
Router(ca-trustpoint)# exit
Router(config)# crypto pki authenticate cisco
 
Enter the base 64 encoded CA certificate.
End with a blank line or the word "quit" on a line by itself
 

(CA certificate text not shown)

quit
Certificate has the following attributes:
Fingerprint MD5: A2339B4C 747873D4 6CE7C1F3 8DCB5CE9
Fingerprint SHA1: 85371CA6 E550143D CE280347 1BDE3A09 E8F8770F
 
% Do you accept this certificate? [yes/no]: yes
Trustpoint CA certificate accepted.
% Certificate successfully imported
 
Router(config)# end
Router# copy running-config startup-config

Start Smart Call Home Registration

To start the Smart Call Home registration process, manually send an inventory alert-group message to the CiscoTAC-1 profile.

SUMMARY STEPS

1. call-home send alert-group inventory profile CiscoTAC-1

DETAILED STEPS

Command or Action
Purpose

Step 1

call-home send alert-group inventory profile CiscoTAC-1

 

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

Sends an inventory alert group message to the CiscoTAC-1 destination profile.

What To Do Next

To receive an email from Cisco Systems and follow the instructions to complete the device registration in the Smart Call Home web application:

  • Launch the Smart Call Home web application at the following URL:

https://tools.cisco.com/sch/

  • Accept the Legal Agreement.
  • Confirm device registration for Call Home devices with pending registration.

For more information about using the Smart Call Home web application, see Smart Call Home User Guide . This user guide also includes configuration examples for sending Smart Call Home messages directly from your device or through a transport gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices must not be connected directly to the Internet.

Displaying Call Home Configuration Information

You can use variations of the show call-home command to display Call Home configuration information.

To display the configured Call Home information, use one or more of the following commands:

SUMMARY STEPS

1. show call-home

2. show call-home detail

3. show call-home alert-group

4. show call-home mail-server status

5. show call-home profile { all | name }

6. show call-home statistics

DETAILED STEPS

Command or Action
Purpose

Step 1

show call-home

 

Router# show call-home

Displays the Call Home configuration in summary.

Step 2

show call-home detail

 

Router# show call-home detail

Displays the Call Home configuration in detail.

Step 3

show call-home alert-group

 

Router# show call-home alert-group

Displays the available alert groups and their status.

Step 4

show call-home mail-server status

 

Router# show call-home mail-server status

Checks and displays the availability of the configured e-mail server(s).

Step 5

show call-home profile { all | name }

 

Router# show call-home profile all

Displays the configuration of the specified destination profile. Use the all keyword to display the configuration of all destination profiles.

Step 6

show call-home statistics

 

Router# show call-home statistics

Displays the statistics of Call Home events.

Examples

The following examples show the sample output when using different options of the show call-home command.

Configured Call Home Information in Summary
Router# show call-home
Current call home settings:
call home feature : disable
call home message's from address: username@example.com
call home message's reply-to address: username@example.com
 
vrf for call-home messages: Mgmt-intf
 
contact person's email address: username@example.com
 
contact person's phone number: +14085551234
street address: 1234 Any Street Any city Any state 12345
customer ID: customer@example.com
contract ID: 123456789
site ID: example.com
Mail-server[1]: Address: smtp.example.com Priority: 1
Mail-server[2]: Address: 192.168.0.1 Priority: 2
Rate-limit: 20 message(s) per minute
 
Available alert groups:
Keyword State Description
------------------------ ------- -------------------------------
configuration Enable configuration info
diagnostic Enable diagnostic info
environment Enable environmental info
inventory Enable inventory info
syslog Enable syslog info
 
Profiles:
Profile Name: campus-noc
Profile Name: CiscoTAC-1
Configured Call Home Information in Detail
Router# show call-home detail
Current call home settings:
call home feature : disable
call home message's from address: username@example.com
call home message's reply-to address: username@example.com
 
vrf for call-home messages: Mgmt-intf
 
contact person's email address: username@example.com
 
contact person's phone number: +14085551234
street address: 1234 Any Street Any city Any state 12345
customer ID: customer@example.com
contract ID: 123456789
site ID: example.com
Mail-server[1]: Address: smtp.example.com Priority: 1
Mail-server[2]: Address: 192.168.0.1 Priority: 2
Rate-limit: 20 message(s) per minute
 
Available alert groups:
Keyword State Description
------------------------ ------- -------------------------------
configuration Enable configuration info
diagnostic Enable diagnostic info
environment Enable environmental info
inventory Enable inventory info
syslog Enable syslog info
 
Profiles:
 
Profile Name: campus-noc
Profile status: ACTIVE
Preferred Message Format: long-text
Message Size Limit: 3145728 Bytes
Transport Method: email
Email address(es): username@example.com
HTTP address(es): Not yet set up
 
Alert-group Severity
------------------------ ------------
inventory normal
 
Syslog-Pattern Severity
------------------------ ------------
N/A N/A
 
Profile Name: CiscoTAC-1
Profile status: INACTIVE
Preferred Message Format: xml
Message Size Limit: 3145728 Bytes
Transport Method: email
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 23 day of the month at 10:28
 
Periodic inventory info message is scheduled every 23 day of the month at 10:13
 
Alert-group Severity
------------------------ ------------
diagnostic minor
environment minor
inventory normal
 
Syslog-Pattern Severity
------------------------ ------------
.* major
Available Call Home Alert Groups
Router# show call-home alert-group
Available alert groups:
Keyword State Description
------------------------ ------- -------------------------------
configuration Enable configuration info
diagnostic Enable diagnostic info
environment Enable environmental info
inventory Enable inventory info
syslog Enable syslog info
E-Mail Server Status Information
Router# show call-home mail-server status
Please wait. Checking for mail server status ...
 
Translating "smtp.example.com"
Mail-server[1]: Address: smtp.example.com Priority: 1 [Not Available]
Mail-server[2]: Address: 192.168.0.1 Priority: 2 [Not Available]
Information About All Destination Profiles (Predefined and User-Defined)
Router# show call-home profile all
 
Profile Name: campus-noc
Profile status: ACTIVE
Preferred Message Format: long-text
Message Size Limit: 3145728 Bytes
Transport Method: email
Email address(es): username@example.com
HTTP address(es): Not yet set up
 
Alert-group Severity
------------------------ ------------
inventory normal
 
Syslog-Pattern Severity
------------------------ ------------
N/A N/A
 
Profile Name: CiscoTAC-1
Profile status: INACTIVE
Preferred Message Format: xml
Message Size Limit: 3145728 Bytes
Transport Method: email
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 23 day of the month at 12:13
 
Periodic inventory info message is scheduled every 23 day of the month at 11:58
 
Alert-group Severity
------------------------ ------------
diagnostic minor
environment minor
inventory normal
 
Syslog-Pattern Severity
------------------------ ------------
.* major
 
Router#
Information About a User-Defined Destination Profile
Router# show call-home profile campus-noc
 
Profile Name: campus-noc
Profile status: ACTIVE
Preferred Message Format: long-text
Message Size Limit: 3145728 Bytes
Transport Method: email
Email address(es): username@example.com
HTTP address(es): Not yet set up
 
Alert-group Severity
------------------------ ------------
inventory normal
 
Syslog-Pattern Severity
------------------------ ------------
N/A N/A
Call Home Statistics
Router# show call-home statistics
Message Types Total Email HTTP
------------- -------------------- -------------------- ------------------
Total Success 6 6 0
Config 4 4 0
Diagnostic 0 0 0
Environment 0 0 0
Inventory 2 2 0
SysLog 0 0 0
Test 0 0 0
Request 0 0 0
Send-CLI 0 0 0
 
Total In-Queue 0 0 0
Config 0 0 0
Diagnostic 0 0 0
Environment 0 0 0
Inventory 0 0 0
SysLog 0 0 0
Test 0 0 0
Request 0 0 0
Send-CLI 0 0 0
 
Total Failed 0 0 0
Config 0 0 0
Diagnostic 0 0 0
Environment 0 0 0
Inventory 0 0 0
SysLog 0 0 0
Test 0 0 0
Request 0 0 0
Send-CLI 0 0 0
 
Total Ratelimit
-dropped 0 0 0
Config 0 0 0
Diagnostic 0 0 0
Environment 0 0 0
Inventory 0 0 0
SysLog 0 0 0
Test 0 0 0
Request 0 0 0
Send-CLI 0 0 0
 
Last call-home message sent time: 2010-01-11 18:32:32 GMT+00:00

Default Settings

Table 9-2 lists the default Call Home settings.

 

Table 9-2 Default Call Home Settings

Parameters
Default

Call Home feature status

Disabled

User-defined profile status

Active

Predefined Cisco TAC profile status

Inactive

Transport method

E-mail

Message format type

XML

Destination message size for a message sent in long text, short text, or XML format

3,145,728

Alert group status

Enabled

Call Home message severity threshold

0 (debugging)

Message rate limit for messages per minute

20

Alert Group Trigger Events and Commands

Call Home trigger events are grouped into alert groups, with each alert group assigned CLI commands to execute when an event occurs. The CLI command output is included in the transmitted message. Table 9-3 lists the trigger events included in each alert group, including the severity level of each event and the executed CLI commands for the alert group.

 

Table 9-3 Call Home Alert Groups, Events, and Actions

Alert Group
Call Home Trigger Event
Syslog Event
Severity
Description and CLI Commands Executed

Configuration

User-generated request for configuration. (Sent to TAC.)

CLI commands executed:

show platform
show inventory
show running-config all
show startup-config
show version

Diagnostic

CLI commands executed:

show platform
show diagnostic result slot x detail
show version
show inventory
show buffers
show logging
show diagnostic result slot all
show diagnostic events slot all

Error Counter Monitoring Test failure count exceeds threshold

%ASR1000_RP_DIAG_TEST-4- ERR_CNTR_HM_TEST_FAIL

4

ERROR_COUNTER_WARNING: Slot number Error counter exceeds threshold, system operation continue.

Error Counter Monitoring Test failure count exceeds threshold

%ASR1000_RP_DIAG_TEST-4- ERR_CNTR_HM_TEST_DATA

4

ERROR_COUNTER_DATA: ID: number IN: number PO: number RE: number RM: number DV: number EG: number CF: number TF: number

Environmental

Events related to power, fan, and environment sensing elements, such as temperature alarms. (Sent to TAC.)

CLI commands executed:

show platform
show environment
show inventory
show logging

%ASR1000_PEM-3-FANFAIL

3

The fan in slot ( slot / subslot number) is encountering a failure condition.

%ASR1000_PEM-6-FANOK

6

The fan in slot ( slot / subslot number) is functioning properly.

%ASR1000_PEM-3-PEMFAIL

3

The PEM in slot ( slot number) is switched off or encountering a failure condition.

%ASR1000_PEM-6-PEMOK

6

The PEM in slot ( slot number) is functioning properly.

%ENVIRONMENTAL-1-ALERT

1

Any sensor in fp/cc/rp has exceeded a certain threshold and resulted in this environmental alert.

ENVM

%ENVIRONMENTAL-1-SENSORFAIL

1

Any sensor in fp/cc/rp has failed and resulted in this environmental alert.

%ENVIRONMENTAL-1-SENSOROK

1

Any sensor in fp/cc/rp has recovered and resulted in this environmental alert.

Inventory

Inventory status should be provided whenever a unit is cold-booted, or when FRUs are inserted or removed. This is considered a noncritical event, and the information is used for status and entitlement. (Sent to TAC.)

CLI commands executed:

show platform
show inventory oid
show version
show diag all eeprom detail

SPA HARDWARE_REMOVAL

%ASR1000_OIR-6-REMSPA

6

SPA removed from subslot ( slot / subslot number) and the interfaces are disabled.

SPA HARDWARE_INSERTION

%ASR1000_OIR-6-INSSPA

6

SPA inserted in subslot ( slot / subslot number).

CC/FP/RP HARDWARE_REMOVAL

%ASR1000_OIR-6-REMCARD

6

Card (cc/rp/fp) removed from slot ( slot number).

CC/FP/RP HARDWARE_INSERTION

%ASR1000_OIR-6-INSCARD

6

Card (cc/rp/fp) inserted in slot ( slot number).

PEM /FM HARDWARE_REMOVAL

%ASR1000_PEM-6-REMPEM_FM

6

PEM/FM slot ( slot number) removed.

PEM /FM HARDWARE_INSERTION

%ASR1000_PEM-6-INSPEM_FM

6

PEM/FM slot ( slot number) inserted.

Syslog

Event logged to syslog.

CLI commands executed:

show inventory
show logging

SYSLOG

LOG_EMERG

0

System is unusable.

SYSLOG

LOG_ALERT

1

Action must be taken immediately.

SYSLOG

LOG_CRIT

2

Critical conditions.

SYSLOG

LOG_ERR

3

Error conditions.

SYSLOG

LOG_WARNING

4

Warning conditions.

SYSLOG

LOG_NOTICE

5

Normal but signification condition.

SYSLOG

LOG_INFO

6

Informational.

SYSLOG

LOG_DEBUG

7

Debug-level messages.

Test

TEST

User-generated test message. (Sent to TAC.)

CLI commands executed:

show platform
show inventory
show version

Message Contents

The following tables display the content formats of alert group messages:

  • Table 9-4 describes the content fields of a short text message.
  • Table 9-5 describes the content fields that are common to all long text and XML messages. The fields specific to a particular alert group message are inserted at a point between the common fields. The insertion point is identified in the table.
  • Table 9-6 describes the inserted content fields for reactive messages (system failures that require a TAC case) and proactive messages (issues that might result in degraded system performance).
  • Table 9-7 describes the inserted content fields for an inventory message.

This section also includes the following subsections that provide sample messages:

 

Table 9-4 Format for a Short Text Message

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 a system message

 

Table 9-5 Common Fields for All Long Text and XML Messages

Data Item
(Plain Text and XML)
Description
(Plain Text and XML)
MML 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. Specific event names are listed in the “Alert Group Trigger Events and Commands” section.

For short text message only

Message type

Specifically “Call Home”.

CallHome/Event/Type

Message subtype

Specific type of message: full, delta, test

CallHome/Event/SubType

Message group

Specifically “reactive”. Optional, because default is “reactive”.

Not applicable. For long-text message only

Severity level

Severity level of message (see Table 9-1 ).

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 end device generating message. This field should be empty if the message is nonspecific to a fabric switch. The format is type @ Sid @ seria l.

    • type is the product model number from 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.

Example: ASR1006@C@FOX105101DH

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 site IDs supplied by Cisco Systems or other data meaningful to alternate support services.

CallHome/CustomerData/
ContractData/SiteId

Server ID

If the message is generated from the fabric switch, this is the unique device identifier (UDI) of the switch.

The format is type @ Sid @ seria l.

    • type is the product model number from 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.

Example: ASR1006@C@FOX105101DH

For long text message only

Message description

Short text describing the error.

CallHome/MessageDescription

Device name

Node that experienced the event. This is the host name of the device.

CallHome/CustomerData/
SystemInfo/NameName

Contact name

Name of person to contact for issues associated with the node experiencing the event.

CallHome/CustomerData/
SystemInfo/Contact

Contact e-mail

E-mail address of person identified as 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 containing street address for RMA part shipments associated with this unit.

CallHome/CustomerData/
SystemInfo/StreetAddress

Model name

Model name of the router. This is 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.

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

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”

Fields specific to a particular alert group message are inserted here.

The following fields may be repeated if multiple CLI commands are executed for this alert group.

Command output name

The exact name of the issued CLI command.

/aml/Attachments/Attachment/Name

Attachment type

Attachment type. Usually “inline”.

/aml/Attachments/Attachment@type

MIME type

Normally “text” or “plain” or encoding type.

/aml/Attachments/Attachment/
Data@encoding

Command output text

Output of command automatically executed (see Table 9-3 ).

/mml/attachments/attachment/atdata

 

Table 9-6 Inserted Fields for a Reactive or Proactive Event Message

Data Item
(Plain Text and XML)
Description
(Plain Text and XML)
MML Tag
(XML Only)

Chassis hardware version

Hardware version of chassis.

CallHome/Device/Cisco_Chassis/
HardwareVersion

Supervisor module software version

Top-level software version.

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

Affected FRU name

Name of the affected FRU generating the event message.

CallHome/Device/Cisco_Chassis/
Cisco_Card/Model

Affected FRU serial number

Serial number of affected FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/SerialNumber

Affected FRU part number

Part number of affected FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/PartNumber

FRU slot

Slot number of FRU generating the event message.

CallHome/Device/Cisco_Chassis/
Cisco_Card/LocationWithinContainer

FRU hardware version

Hardware version of affected FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/HardwareVersion

FRU software version

Software version(s) running on affected FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/SoftwareIdentity/
VersionString

 

Table 9-7 Inserted Fields for an Inventory Event Message

Data Item
(Plain Text and XML)
Description
(Plain Text and XML)
MML Tag
(XML Only)

Chassis hardware version

Hardware version of chassis.

CallHome/Device/Cisco_Chassis/
HardwareVersion

Supervisor module software version

Top-level software version.

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

FRU name

Name of the affected FRU generating the event message.

CallHome/Device/Cisco_Chassis/
Cisco_Card/Model

FRU s/n

Serial number of FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/SerialNumber

FRU part number

Part number of FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/PartNumber

FRU slot

Slot number of FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/LocationWithinContainer

FRU hardware version

Hardware version of FRU.

CallHome/Device/Cisco_Chassis/
CiscoCard/HardwareVersion

FRU software version

Software version(s) running on FRU.

CallHome/Device/Cisco_Chassis/
Cisco_Card/SoftwareIdentity/
VersionString

Sample Syslog Alert Notification in Long Text Format

The following example shows a Syslog alert notification in long text format:

TimeStamp : 2009-12-03 12:26 GMT+05:00
Message Name : syslog
Message Type : Call Home
Message Group : reactive
Severity Level : 2
Source ID : ASR1000
Device ID : ASR1006@C@FOX105101DH
Customer ID : username@example.com
Contract ID : 123456789
Site ID : example.com
Server ID : ASR1006@C@FOX105101DH
Event Description : *Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console
System Name : mcp-6ru-3
Contact Email : username@example.com
Contact Phone : +14085551234
Street Address : 1234 Any Street Any City Any State 12345
Affected Chassis : ASR1006
Affected Chassis Serial Number : FOX105101DH
Affected Chassis Part No : 68-2584-05
Affected Chassis Hardware Version : 2.1
Command Output Name : show logging
Attachment Type : command output
MIME Type : text/plain
Command Output Text :
Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
 
No Active Message Discriminator.
 
 
 
No Inactive Message Discriminator.
 
 
Console logging: disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 112 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, 104 message lines logged
 
Log Buffer (1000000 bytes):
 
*Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED
*Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001
*Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun
 
*Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up
*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up
*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up
*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down
*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up
*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up
*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up
*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager
*Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware
*Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe
*Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success.
*Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete
*Dec 3 07:16:33.532: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:33.786: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete
*Dec 3 07:16:34.158: %IOSXE-6-PLATFORM: F1: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 3 07:16:35.134: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 3 07:16:38.965: %CMRP-6-FP_HA_STATUS: R0/0: cmand: F0 redundancy state is Active with ready Standby
*Dec 3 07:17:01.926: %DYNCMD-7-PKGINT_INSTALLED: The command package 'platform_trace' has been succesfully installed
*Dec 3 12:17:05.385 IST: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:17:05 UTC Thu Dec 3 2009 to 12:17:05 IST Thu Dec 3 2009, configured from console by console.
*Dec 3 12:17:05.506 IST: %SYS-5-CONFIG_I: Configured from memory by console
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 2/3, interfaces disabled
*Dec 3 12:17:05.514 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-8XOC3-POS) offline in subslot 0/2
*Dec 3 12:17:05.515 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XOC3-POS) offline in subslot 1/3
*Dec 3 12:17:05.516 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 2/3
*Dec 3 12:17:05.520 IST: %ASR1000_OIR-6-INSCARD: Card (rp) inserted in slot R1
*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F0
*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F1
*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F1
*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 0
*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Dec 3 12:17:05.576 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2
*Dec 3 12:17:05.580 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 1
*Dec 3 12:17:05.581 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 2
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 2
*Dec 3 12:17:05.583 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 2/3
*Dec 3 12:17:05.844 IST: %SYS-5-RESTART: System restarted --
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 18-Nov-09 01:14 by
*Dec 3 12:17:06.005 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Dec 3 12:17:06.005 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Dec 3 12:16:30.097 IST: %LINK-3-UPDOWN: SIP2/3: Interface EOBC2/1, changed state to up
*Dec 3 12:16:27.595 IST: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up
*Dec 3 12:16:26.420 IST: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up
*Dec 3 12:17:07.435 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Dec 3 12:17:07.435 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Dec 3 12:17:07.476 IST: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Dec 3 12:17:08.137 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XOC3-POS) online in subslot 1/3
*Dec 3 12:17:08.139 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-8XOC3-POS) online in subslot 0/2
*Dec 3 12:17:08.346 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 2/3
*Dec 3 12:17:08.491 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Dec 3 12:17:11.047 IST: %SYS-6-BOOTTIME: Time taken to reboot after reload = 12319 seconds
*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: xinetd Version 2.3.14 started with no options compiled in.
*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: Started working: 1 available service
*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: xinetd Version 2.3.14 started with no options compiled in.
*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: Started working: 2 available services
*Dec 3 12:17:13.753 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/1, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/2, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/3, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/4, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/5, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/6, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/7, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/1, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/2, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/3, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/4, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/5, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/6, changed state to down
*Dec 3 12:17:14.755 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/7, changed state to down
*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/1: SLOS declared
*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/2: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/3: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/4: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/5: SLOS declared
*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/6: SLOS declared
*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/7: SLOS declared
*Dec 3 12:17:14.850 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to down
*Dec 3 12:17:14.851 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to down
*Dec 3 12:17:16.069 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to up
*Dec 3 12:17:15.734 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/0, changed state to up
*Dec 3 12:17:16.868 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to up
*Dec 3 12:17:16.905 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to up
*Dec 3 12:17:16.538 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/7, changed state to down
*Dec 3 12:17:17.070 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to up
*Dec 3 12:17:16.488 IST: %LINK-3-UPDOWN: SIP1/3: Interface POS1/3/0, changed state to up
*Dec 3 12:17:17.868 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to up
*Dec 3 12:17:16.199 IST: %LINK-3-UPDOWN: SIP2/3: Interface POS2/3/0, changed state to up
*Dec 3 12:17:17.905 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to up
*Dec 3 12:22:01.574 IST: %IP-4-DUPADDR: Duplicate address 172.27.55.233 on GigabitEthernet0, sourced by 001a.3044.1ec0
*Dec 3 12:23:47.613 IST: %SYS-5-CONFIG_I: Configured from console by console
*Dec 3 12:24:37.134 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console
*Dec 3 12:25:34.356 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)
*Dec 3 12:25:39.459 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)
*Dec 3 12:25:54.405 IST: %SYS-5-CONFIG_I: Configured from console by console
mcp-6ru-3#
Command Output Name : show inventory
Attachment Type : command output
MIME Type : text/plain
Command Output Text : NAME: "Chassis", DESCR: "Cisco ASR1006 Chassis"
PID: ASR1006 , VID: V00, SN: FOX105101DH
 
NAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: MCP-CC , VID: V00, SN: JAB1104064W
 
NAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"
PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0
 
NAME: "subslot 0/2 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"
PID: SFP-OC3-MM , VID: A , SN: OCP12231628
 
NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: MCP-CC , VID: V00, SN: JAB1104062X
 
NAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"
PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QU
 
NAME: "subslot 1/3 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"
PID: SFP-OC3-MM , VID: A , SN: OCP12310174
 
NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9
 
NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"
PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41L
 
NAME: "subslot 2/3 transceiver 0", DESCR: "OC12 SR-1/STM4 MM"
PID: SFP-OC12-MM , VID: A , SN: OCP10100281
 
NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"
PID: ASR1000-RP1 , VID: V00, SN: JAB11110181
 
NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"
PID: ASR1000-RP1 , VID: V00, SN: JAB1111016K
 
NAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"
PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZX
 
NAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"
PID: ASR1000-ESP10 , VID: V00, SN: JAB111101AP
 
NAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"
PID: TBD000000000000000, VID: +^A , SN: ART1114Q00F
 
NAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"
PID: TBD000000000000000, VID: +^A , SN: ART1115P00D

Sample Syslog Alert Notification in XML Format

The following example shows a 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>M0:FOX105101DH:CEC1E73E</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>2009-12-03 12:29:02 GMT+05:00</aml-block:CreationDate>
<aml-block:Builder>
<aml-block:Name>ASR1000</aml-block:Name>
<aml-block:Version>2.0</aml-block:Version>
</aml-block:Builder>
<aml-block:BlockGroup>
<aml-block:GroupId>G1:FOX105101DH:CEC1E73E</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>2</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>2009-12-03 12:29:01 GMT+05:00</ch:EventTime>
<ch:MessageDescription>*Dec 3 12:29:01.017 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console</ch:MessageDescription>
<ch:Event>
<ch:Type>syslog</ch:Type>
<ch:SubType></ch:SubType>
<ch:Brand>Cisco Systems</ch:Brand>
<ch:Series>ASR1000 Series Routers</ch:Series>
</ch:Event>
<ch:CustomerData>
<ch:UserData>
<ch:Email>username@example.com</ch:Email>
</ch:UserData>
<ch:ContractData>
<ch:CustomerId>username@example.com</ch:CustomerId>
<ch:SiteId>example.com</ch:SiteId>
<ch:ContractId>123456789</ch:ContractId>
<ch:DeviceId>ASR1006@C@FOX105101DH</ch:DeviceId>
</ch:ContractData>
<ch:SystemInfo>
<ch:Name>mcp-6ru-3</ch:Name>
<ch:Contact></ch:Contact>
<ch:ContactEmail>username@example.com</ch:ContactEmail>
<ch:ContactPhoneNumber>+14085551234</ch:ContactPhoneNumber>
<ch:StreetAddress>1234 Any Street Any City Any State 12345</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>ASR1006</rme:Model>
<rme:HardwareVersion>2.1</rme:HardwareVersion>
<rme:SerialNumber>FOX105101DH</rme:SerialNumber>
<rme:AdditionalInformation>
<rme:AD name="PartNumber" value="68-2584-05" />
<rme:AD name="SoftwareVersion" value="" />
<rme:AD name="SystemObjectId" value="1.3.6.1.4.1.9.1.925" />
<rme:AD name="SystemDescription" value="Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 18-Nov-09 01:14 by " />
</rme:AdditionalInformation>
</rme:Chassis>
</ch:Device>
</ch:CallHome>
</aml-block:Content>
<aml-block:Attachments>
<aml-block:Attachment type="inline">
<aml-block:Name>show logging</aml-block:Name>
<aml-block:Data encoding="plain">
<![CDATA[
Syslog logging: enabled (1 messages dropped, 29 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
 
No Active Message Discriminator.
 
 
 
No Inactive Message Discriminator.
 
 
Console logging: disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 114 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, 106 message lines logged
 
Log Buffer (1000000 bytes):
 
*Dec 3 07:16:55.020: ASR1000-RP HA: RF status CID 1340, seq 93, status RF_STATUS_REDUNDANCY_MODE_CHANGE, op 0, state DISABLED, peer DISABLED
*Dec 3 07:17:00.379: %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf Mgmt-intf created with ID 4085, ipv4 table-id 0xFF5, ipv6 table-id 0x1E000001
*Dec 3 07:17:00.398: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available. The network clock has changed to freerun
 
*Dec 3 07:17:00.544: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up
*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface EOBC0, changed state to up
*Dec 3 07:17:00.545: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up
*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Dec 3 07:17:00.546: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down
*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up
*Dec 3 07:17:01.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up
*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up
*Dec 3 07:17:01.558: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Dec 3 07:17:01.818: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded from the Shell Manager
*Dec 3 07:16:30.926: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 2 is pre-release hardware
*Dec 3 07:16:24.147: %HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID: F1: cman_fp: The idprom contains an invalid checksum in a sensor entry. Expected: 63, calculated: fe
*Dec 3 07:16:24.176: %CMFP-3-IDPROM_SENSOR: F1: cman_fp: One or more sensor fields from the idprom failed to parse properly because Success.
*Dec 3 07:16:27.669: %CPPHA-7-START: F1: cpp_ha: CPP 0 preparing image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:27.839: %CPPHA-7-START: F1: cpp_ha: CPP 0 startup init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:28.659: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:28.799: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:32.557: %CPPHA-7-START: F1: cpp_ha: CPP 0 running init image /tmp/sw/fp/1/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:32.812: %CPPHA-7-READY: F1: cpp_ha: CPP 0 loading and initialization complete
*Dec 3 07:16:33.532: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image /tmp/sw/fp/0/0/fp/mount/usr/cpp/bin/cpp-mcplo-ucode
*Dec 3 07:16:33.786: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization complete
*Dec 3 07:16:34.158: %IOSXE-6-PLATFORM: F1: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 3 07:16:35.134: %IOSXE-6-PLATFORM: F0: cpp_cp: Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 3 07:16:38.965: %CMRP-6-FP_HA_STATUS: R0/0: cmand: F0 redundancy state is Active with ready Standby
*Dec 3 07:17:01.926: %DYNCMD-7-PKGINT_INSTALLED: The command package 'platform_trace' has been succesfully installed
*Dec 3 12:17:05.385 IST: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:17:05 UTC Thu Dec 3 2009 to 12:17:05 IST Thu Dec 3 2009, configured from console by console.
*Dec 3 12:17:05.506 IST: %SYS-5-CONFIG_I: Configured from memory by console
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces disabled
*Dec 3 12:17:05.508 IST: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 2/3, interfaces disabled
*Dec 3 12:17:05.514 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-8XOC3-POS) offline in subslot 0/2
*Dec 3 12:17:05.515 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XOC3-POS) offline in subslot 1/3
*Dec 3 12:17:05.516 IST: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 2/3
*Dec 3 12:17:05.520 IST: %ASR1000_OIR-6-INSCARD: Card (rp) inserted in slot R1
*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F0
*Dec 3 12:17:05.521 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-INSCARD: Card (fp) inserted in slot F1
*Dec 3 12:17:05.574 IST: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F1
*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 0
*Dec 3 12:17:05.575 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Dec 3 12:17:05.576 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2
*Dec 3 12:17:05.580 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 1
*Dec 3 12:17:05.581 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-INSCARD: Card (cc) inserted in slot 2
*Dec 3 12:17:05.582 IST: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 2
*Dec 3 12:17:05.583 IST: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 2/3
*Dec 3 12:17:05.844 IST: %SYS-5-RESTART: System restarted --
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Experimental Version 12.2(20091118:075558) [v122_33_xnf_asr_rls6_throttle-mcp_dev_rls6 102]
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 18-Nov-09 01:14 by
*Dec 3 12:17:06.005 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Dec 3 12:17:06.005 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Dec 3 12:16:30.097 IST: %LINK-3-UPDOWN: SIP2/3: Interface EOBC2/1, changed state to up
*Dec 3 12:16:27.595 IST: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up
*Dec 3 12:16:26.420 IST: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up
*Dec 3 12:17:07.435 IST: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Dec 3 12:17:07.435 IST: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Dec 3 12:17:07.476 IST: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Dec 3 12:17:08.137 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XOC3-POS) online in subslot 1/3
*Dec 3 12:17:08.139 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-8XOC3-POS) online in subslot 0/2
*Dec 3 12:17:08.346 IST: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 2/3
*Dec 3 12:17:08.491 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Dec 3 12:17:11.047 IST: %SYS-6-BOOTTIME: Time taken to reboot after reload = 12319 seconds
*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: xinetd Version 2.3.14 started with no options compiled in.
*Dec 3 12:17:11.562 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[879]: Started working: 1 available service
*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: xinetd Version 2.3.14 started with no options compiled in.
*Dec 3 12:17:11.584 IST: %IOSXE-5-PLATFORM: R0/0: xinetd[887]: Started working: 2 available services
*Dec 3 12:17:13.753 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/1, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/2, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/3, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/4, changed state to down
*Dec 3 12:17:13.754 IST: %LINK-3-UPDOWN: Interface POS0/2/5, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/6, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS0/2/7, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to down
*Dec 3 12:17:13.755 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/1, changed state to down
*Dec 3 12:17:14.753 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/2, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/3, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/4, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/5, changed state to down
*Dec 3 12:17:14.754 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/6, changed state to down
*Dec 3 12:17:14.755 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/7, changed state to down
*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/1: SLOS declared
*Dec 3 12:17:14.848 IST: %SONET-4-ALARM: POS0/2/2: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/3: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/4: SLOS declared
*Dec 3 12:17:14.849 IST: %SONET-4-ALARM: POS0/2/5: SLOS declared
*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/6: SLOS declared
*Dec 3 12:17:14.850 IST: %SONET-4-ALARM: POS0/2/7: SLOS declared
*Dec 3 12:17:14.850 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to down
*Dec 3 12:17:14.851 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to down
*Dec 3 12:17:16.069 IST: %LINK-3-UPDOWN: Interface POS0/2/0, changed state to up
*Dec 3 12:17:15.734 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/0, changed state to up
*Dec 3 12:17:16.868 IST: %LINK-3-UPDOWN: Interface POS1/3/0, changed state to up
*Dec 3 12:17:16.905 IST: %LINK-3-UPDOWN: Interface POS2/3/0, changed state to up
*Dec 3 12:17:16.538 IST: %LINK-3-UPDOWN: SIP0/2: Interface POS0/2/7, changed state to down
*Dec 3 12:17:17.070 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/2/0, changed state to up
*Dec 3 12:17:16.488 IST: %LINK-3-UPDOWN: SIP1/3: Interface POS1/3/0, changed state to up
*Dec 3 12:17:17.868 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS1/3/0, changed state to up
*Dec 3 12:17:16.199 IST: %LINK-3-UPDOWN: SIP2/3: Interface POS2/3/0, changed state to up
*Dec 3 12:17:17.905 IST: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS2/3/0, changed state to up
*Dec 3 12:22:01.574 IST: %IP-4-DUPADDR: Duplicate address 172.27.55.233 on GigabitEthernet0, sourced by 001a.3044.1ec0
*Dec 3 12:23:47.613 IST: %SYS-5-CONFIG_I: Configured from console by console
*Dec 3 12:24:37.134 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console
*Dec 3 12:25:34.356 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)
*Dec 3 12:25:39.459 IST: %DIAG-3-TEST_FAIL: slot R0: TestErrorCounterMonitor{ID=1} has failed. Error code = 0x1 (DIAG_FAILURE)
*Dec 3 12:25:54.405 IST: %SYS-5-CONFIG_I: Configured from console by console
*Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console
*Dec 3 12:28:56.057 IST: %SYS-5-CONFIG_I: Configured from console by console
mcp-6ru-3#]]></aml-block:Data>
</aml-block:Attachment>
<aml-block:Attachment type="inline">
<aml-block:Name>show inventory</aml-block:Name>
<aml-block:Data encoding="plain">
<![CDATA[NAME: "Chassis", DESCR: "Cisco ASR1006 Chassis"
PID: ASR1006 , VID: V00, SN: FOX105101DH
 
NAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: MCP-CC , VID: V00, SN: JAB1104064W
 
NAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"
PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0
 
NAME: "subslot 0/2 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"
PID: SFP-OC3-MM , VID: A , SN: OCP12231628
 
NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: MCP-CC , VID: V00, SN: JAB1104062X
 
NAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"
PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QU
 
NAME: "subslot 1/3 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"
PID: SFP-OC3-MM , VID: A , SN: OCP12310174
 
NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"
PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9
 
NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"
PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41L
 
NAME: "subslot 2/3 transceiver 0", DESCR: "OC12 SR-1/STM4 MM"
PID: SFP-OC12-MM , VID: A , SN: OCP10100281
 
NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"
PID: ASR1000-RP1 , VID: V00, SN: JAB11110181
 
NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"
PID: ASR1000-RP1 , VID: V00, SN: JAB1111016K
 
NAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"
PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZX
 
NAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"
PID: ASR1000-ESP10 , VID: V00, SN: JAB111101AP
 
NAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"
PID: TBD000000000000000, VID: +^A , SN: ART1114Q00F
 
NAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"
PID: TBD000000000000000, VID: +^A , SN: ART1115P00D
 
Router#]]></aml-block:Data>
</aml-block:Attachment>
</aml-block:Attachments>
</aml-block:Block>
</soap-env:Body>
</soap-env:Envelope>

Additional References

The following sections provide references related to the Call Home feature.

Related Documents

Related Topic
Title

Cisco IOS XE commands

Cisco IOS Master Commands List, All Releases

Explains how the Smart Call Home service offers web-based access to important information on select Cisco devices and offers higher network availability, and increased operational efficiency by providing proactive diagnostics and real-time alerts.

Smart Call Home User Guide

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

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

Public Key Infrastructure (PKI) and Certificate Authority configuration in Cisco IOS XE software

Cisco IOS XE Security Configuration Guide: Secure Connectivity

Standards

Standard
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

MIBs

MIB
MIBs Link

CISCO-CALLHOME-MIB

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

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

RFCs

RFC
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

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.

To receive security and technical information about your products, you can subscribe to various services, such as 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/cisco/web/support/index.html

Feature Information for Call Home

Table 9-8 lists the release history for this feature on the Cisco ASR 1000 Series Routers.

For information on a feature in this technology that is not documented here, see the Cisco ASR 1000 Series Aggregation Services Routers Documentation Roadmap .

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


Note Table 9-8 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.


 

Table 9-8 Feature Information for Call Home

Feature Name
Releases
Feature Information

Call Home

IOS XE Release 2.6

Call Home provides e-mail-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard e-mail, or XML-based automated parsing applications.

In Cisco IOS XE Release 2.6, support for this feature was added for the Cisco ASR 1000 Series Aggregation Services Routers.

The following commands are new or modified: show diagnostic commands.