-
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
-
Preface
-
Software Packaging and Architecture
-
Using Cisco IOS XE Software
-
Console Port, Telnet, and SSH Handling
-
Consolidated Packages and Sub-Package Management
-
Software Upgrade Process
-
High Availability Overview
-
Broadband Scalability and Performance
-
Configuring Cisco License Call Home
-
Configuring Call Home
-
Configuring Cisco Right-To-Use License
-
Intelligent Wireless Access Gateway on ASR 1000 Routers for Service Provider WiFi Offload
-
UniDirectional Link Detection (UDLD) Protocol
-
Using the Management Ethernet Interface
-
Synchronous Ethernet Support
-
Configuring Ethernet Over Soft GRE
-
Configuring Bridge Domain Interfaces
-
Monitoring and Maintaining Multilink Frame Relay
-
Configuring MPLS Layer 2 VPNs
-
LSM-MLDP-based MVPN Support
-
Tracing and Trace Management
-
Configuring and Accessing the Web User Interface
-
Unsupported Commands
-
Configuration Examples
-
Feedback
Table Of Contents
How to Obtain Smart Call Home Service
Configuring the Management Interface VRF
Configuring a Destination Profile
Configuring a Destination Profile to Send Email Messages
Configuring a Destination Profile to Send HTTP Messages
Working With Destination Profiles
Configuring Contact Information
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
Configure and Enable Call Home
Declare and Authenticate a CA Trustpoint
Start Smart Call Home Registration
Displaying Call Home Configuration Information
Alert Group Trigger Events and Commands
Sample Syslog Alert Notification in Long Text Format
Sample Syslog Alert Notification in XML Format
Feature Information for Call Home
Configuring Call Home
Revised: November 28, 2012
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.
Contents
This guide includes the following sections:
•
How To Configure Call Home to Support the Smart Call Home Service
•
•
•
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:
•
–
–
–
•
•
•
•
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:
•
•
•
•
•
You need the following items to register:
•
•
•
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:
•
•
•
•
•
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.
2.
3.
4.
or
ipv6 address {X:X:X:X::X link-local | X:X:X:X::X/prefix [anycast | eui-64] | autoconfig [default]}
DETAILED STEPS
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 "Using the Management Ethernet Interface" 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
You can configure the following attributes for a destination profile:
•
•
–
–
•
•
•
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:
•
•
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
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 terminalEnter 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.
2.
3.
DETAILED STEPS
Configuring a Destination Profile for E-mail
To configure a destination profile for e-mail transport, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
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.
2.
3.
4.
DETAILED STEPS
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.
2.
3.
DETAILED STEPS
Configuring a Destination Profile for HTTP
To configure a destination profile for http transport, complete the following steps:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
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.
2.
3.
4.
5.
6.
DETAILED STEPS
Copying a Destination Profile
To create a new destination profile by copying an existing profile, complete the following steps:
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Renaming a Destination Profile
To change the name of an existing profile, complete the following steps:
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
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 terminalRouter(config)# call-homeRouter(config-call-home)# profile CiscoTAC-1Router(cfg-call-home-profile)# destination transport-method httpRouter(cfg-call-home-profile)# activeFor 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:
•
•
•
•
•
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
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:
•
•
•
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
Table 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
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.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
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.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Example
The following example shows the configuration of contact information:
Router# configure terminalEnter 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.
2.
3.
DETAILED STEPS
Enabling and Disabling Call Home
To enable or disable the Call Home feature, complete the following steps:
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
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.
DETAILED STEPS
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:
•
•
•
•
To manually trigger Call Home alert group messages, complete the following steps:
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
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:
•
•
•
–
–
–
–
To submit a request for analysis and report information from the Cisco Output Interpreter tool, complete the following steps:
SUMMARY STEPS
1.
2.
DETAILED STEPS
Example
The following example shows a request for analysis of a user-specified show command:
Router# call-home request output-analysis "show diag" profile TGSending 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:
•
•
•
To execute a CLI command and e-mail the command output, complete the following step:
SUMMARY STEPS
1.
DETAILED STEPS
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:
•
•
•
MIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJKoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVowgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9ZmDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAEaMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcyM83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZnBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzoKQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+RxBrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9Configure 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.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
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.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Examples
The following example shows the configuration for declaring and authenticating the Cisco server security certificate:
Router# configure terminalRouter(config)# crypto pki trustpoint ciscoRouter(ca-trustpoint)# enrollment terminalRouter(ca-trustpoint)# exitRouter(config)# crypto pki authenticate ciscoEnter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itselfMIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJKoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVowgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9ZmDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAEaMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcyM83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZnBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzoKQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+RxBrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9quitCertificate has the following attributes:Fingerprint MD5: A2339B4C 747873D4 6CE7C1F3 8DCB5CE9Fingerprint SHA1: 85371CA6 E550143D CE280347 1BDE3A09 E8F8770F% Do you accept this certificate? [yes/no]: yesTrustpoint CA certificate accepted.% Certificate successfully importedRouter(config)# endRouter# copy running-config startup-configStart 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.
DETAILED STEPS
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:
•
•
•
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.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The following examples show the sample output when using different options of the show call-home command.
Example: Configured Call Home Information in SummaryRouter# show call-homeCurrent call home settings:call home feature : disablecall home message's from address: username@example.comcall home message's reply-to address: username@example.comvrf for call-home messages: Mgmt-intfcontact person's email address: username@example.comcontact person's phone number: +14085551234street address: 1234 Any Street Any city Any state 12345customer ID: customer@example.comcontract ID: 123456789site ID: example.comMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Enable configuration infodiagnostic Enable diagnostic infoenvironment Enable environmental infoinventory Enable inventory infosyslog Enable syslog infoProfiles:Profile Name: campus-nocProfile Name: CiscoTAC-1Example: Configured Call Home Information in DetailRouter# show call-home detailCurrent call home settings:call home feature : disablecall home message's from address: username@example.comcall home message's reply-to address: username@example.comvrf for call-home messages: Mgmt-intfcontact person's email address: username@example.comcontact person's phone number: +14085551234street address: 1234 Any Street Any city Any state 12345customer ID: customer@example.comcontract ID: 123456789site ID: example.comMail-server[1]: Address: smtp.example.com Priority: 1Mail-server[2]: Address: 192.168.0.1 Priority: 2Rate-limit: 20 message(s) per minuteAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Enable configuration infodiagnostic Enable diagnostic infoenvironment Enable environmental infoinventory Enable inventory infosyslog Enable syslog infoProfiles:Profile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesTransport Method: emailEmail address(es): username@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesTransport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEServicePeriodic configuration info message is scheduled every 23 day of the month at 10:28Periodic inventory info message is scheduled every 23 day of the month at 10:13Alert-group Severity------------------------ ------------diagnostic minorenvironment minorinventory normalSyslog-Pattern Severity------------------------ ------------.* majorExample: Available Call Home Alert GroupsRouter# show call-home alert-groupAvailable alert groups:Keyword State Description------------------------ ------- -------------------------------configuration Enable configuration infodiagnostic Enable diagnostic infoenvironment Enable environmental infoinventory Enable inventory infosyslog Enable syslog infoExample: E-Mail Server Status InformationRouter# show call-home mail-server statusPlease 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]Example: Information About All Destination Profiles (Predefined and User-Defined)Router# show call-home profile allProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesTransport Method: emailEmail address(es): username@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AProfile Name: CiscoTAC-1Profile status: INACTIVEPreferred Message Format: xmlMessage Size Limit: 3145728 BytesTransport Method: emailEmail address(es): callhome@cisco.comHTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEServicePeriodic configuration info message is scheduled every 23 day of the month at 12:13Periodic inventory info message is scheduled every 23 day of the month at 11:58Alert-group Severity------------------------ ------------diagnostic minorenvironment minorinventory normalSyslog-Pattern Severity------------------------ ------------.* majorRouter#Example: Information About a User-Defined Destination ProfileRouter# show call-home profile campus-nocProfile Name: campus-nocProfile status: ACTIVEPreferred Message Format: long-textMessage Size Limit: 3145728 BytesTransport Method: emailEmail address(es): username@example.comHTTP address(es): Not yet set upAlert-group Severity------------------------ ------------inventory normalSyslog-Pattern Severity------------------------ ------------N/A N/AExample: Call Home StatisticsRouter# show call-home statisticsMessage Types Total Email HTTP------------- -------------------- -------------------- ------------------Total Success 6 6 0Config 4 4 0Diagnostic 0 0 0Environment 0 0 0Inventory 2 2 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total In-Queue 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total Failed 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Total Ratelimit-dropped 0 0 0Config 0 0 0Diagnostic 0 0 0Environment 0 0 0Inventory 0 0 0SysLog 0 0 0Test 0 0 0Request 0 0 0Send-CLI 0 0 0Last call-home message sent time: 2010-01-11 18:32:32 GMT+00:00Default Settings
Table 2 lists the default Call Home settings.
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 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.
Message Contents
The following tables display the content formats of alert group messages:
•
•
•
•
This section also includes the following subsections that provide sample messages:
•
•
Table 5 Common Fields for All Long Text and XML Messages
(Plain Text and XML)
(Plain Text and XML)
(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 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@serial.
•
•
•
•
Example: ASR1006@C@FOX105101DH
CallHome/CustomerData/
ContractData/DeviceIdCustomer ID
Optional user-configurable field used for contract information or other ID by any support service.
CallHome/CustomerData/
ContractData/CustomerIdContract ID
Optional user-configurable field used for contract information or other ID by any support service.
CallHome/CustomerData/
ContractData/ContractIdSite ID
Optional user-configurable field used for site IDs supplied by Cisco Systems or other data meaningful to alternate support services.
CallHome/CustomerData/
ContractData/SiteIdServer 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@serial.
•
•
•
•
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/NameNameContact name
Name of person to contact for issues associated with the node experiencing the event.
CallHome/CustomerData/
SystemInfo/ContactContact e-mail
E-mail address of person identified as contact for this unit.
CallHome/CustomerData/
SystemInfo/ContactEmailContact phone number
Phone number of the person identified as the contact for this unit.
CallHome/CustomerData/
SystemInfo/ContactPhoneNumberStreet address
Optional field containing street address for RMA part shipments associated with this unit.
CallHome/CustomerData/
SystemInfo/StreetAddressModel name
Model name of the router. This is the "specific model as part of a product family name.
CallHome/Device/Cisco_Chassis/
ModelSerial number
Chassis serial number of the unit.
CallHome/Device/Cisco_Chassis/
SerialNumberChassis 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@encodingCommand output text
Output of command automatically executed (see Table 3).
/mml/attachments/attachment/atdata
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:00Message Name : syslogMessage Type : Call HomeMessage Group : reactiveSeverity Level : 2Source ID : ASR1000Device ID : ASR1006@C@FOX105101DHCustomer ID : username@example.comContract ID : 123456789Site ID : example.comServer ID : ASR1006@C@FOX105101DHEvent Description : *Dec 3 12:26:02.319 IST: %CLEAR-5-COUNTERS: Clear counter on all interfaces by consoleSystem Name : mcp-6ru-3Contact Email : username@example.comContact Phone : +14085551234Street Address : 1234 Any Street Any City Any State 12345Affected Chassis : ASR1006Affected Chassis Serial Number : FOX105101DHAffected Chassis Part No : 68-2584-05Affected Chassis Hardware Version : 2.1Command Output Name : show loggingAttachment Type : command outputMIME Type : text/plainCommand 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: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 112 messages logged, xml disabled,filtering disabledException Logging: size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledNo active filter modules.Trap logging: level informational, 104 message lines loggedLog 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 consolemcp-6ru-3#Command Output Name : show inventoryAttachment Type : command outputMIME Type : text/plainCommand Output Text : NAME: "Chassis", DESCR: "Cisco ASR1006 Chassis"PID: ASR1006 , VID: V00, SN: FOX105101DHNAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104064WNAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0NAME: "subslot 0/2 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"PID: SFP-OC3-MM , VID: A , SN: OCP12231628NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104062XNAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QUNAME: "subslot 1/3 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"PID: SFP-OC3-MM , VID: A , SN: OCP12310174NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41LNAME: "subslot 2/3 transceiver 0", DESCR: "OC12 SR-1/STM4 MM"PID: SFP-OC12-MM , VID: A , SN: OCP10100281NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB11110181NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB1111016KNAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZXNAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111101APNAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"PID: TBD000000000000000, VID: +^A , SN: ART1114Q00FNAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"PID: TBD000000000000000, VID: +^A , SN: ART1115P00DSample 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: disabledMonitor logging: level debugging, 0 messages logged, xml disabled,filtering disabledBuffer logging: level debugging, 114 messages logged, xml disabled,filtering disabledException Logging: size (4096 bytes)Count and timestamp logging messages: disabledPersistent logging: disabledNo active filter modules.Trap logging: level informational, 106 message lines loggedLog 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 consolemcp-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: FOX105101DHNAME: "module 0", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104064WNAME: "SPA subslot 0/2", DESCR: "8-port OC3/STM1 POS Shared Port Adapter"PID: SPA-8XOC3-POS , VID: V01, SN: JAE1236TSW0NAME: "subslot 0/2 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"PID: SFP-OC3-MM , VID: A , SN: OCP12231628NAME: "module 1", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: MCP-CC , VID: V00, SN: JAB1104062XNAME: "SPA subslot 1/3", DESCR: "4-port OC3/STM1 POS Shared Port Adapter"PID: SPA-4XOC3-POS , VID: V01, SN: JAB085202QUNAME: "subslot 1/3 transceiver 0", DESCR: "OC3 SR-1/STM1 MM"PID: SFP-OC3-MM , VID: A , SN: OCP12310174NAME: "module 2", DESCR: "Cisco ASR1000 SPA Interface Processor 10"PID: ASR1000-SIP10 , VID: V00, SN: JAB113701L9NAME: "SPA subslot 2/3", DESCR: "1-port OC12/STM4 POS Shared Port Adapter"PID: SPA-1XOC12-POS , VID: V01, SN: JAE1236U41LNAME: "subslot 2/3 transceiver 0", DESCR: "OC12 SR-1/STM4 MM"PID: SFP-OC12-MM , VID: A , SN: OCP10100281NAME: "module R0", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB11110181NAME: "module R1", DESCR: "Cisco ASR1000 Route Processor 1"PID: ASR1000-RP1 , VID: V00, SN: JAB1111016KNAME: "module F0", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111801ZXNAME: "module F1", DESCR: "Cisco ASR1000 Embedded Services Processor, 10Gbps"PID: ASR1000-ESP10 , VID: V00, SN: JAB111101APNAME: "Power Supply Module 0", DESCR: "Cisco ASR1006 AC Power Supply"PID: TBD000000000000000, VID: +^A , SN: ART1114Q00FNAME: "Fan Module 1", DESCR: "Cisco ASR1006 Fan Module"PID: TBD000000000000000, VID: +^A , SN: ART1115P00DRouter#]]></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
Cisco IOS XE commands
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 site page on Cisco.com for access to all related product information.
Public Key Infrastructure (PKI) and Certificate Authority configuration in Cisco IOS XE software
Cisco IOS XE Security Configuration Guide: Secure Connectivity
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
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:
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Call Home
Table 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
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
Copyright © 2008 - 2012 Cisco Systems, Inc. All rights reserved.
