Showing results for 
Search instead for 
Did you mean: 

Welcome to the Smart Call Home Community!

Our online forum for Smart Call Home customers to share, learn, and collaborate on Smart Call Home related topics. We encourage you to ask questions of Cisco experts, start a discussion, or share ideas and insight.

Smart Call Home enabled devices perform proactive diagnostics on their own components to provide real-time alerts and remediation advice when an issue is detected. An embedded support feature available on a broad range of Cisco products, it is provided at no additional cost with an active Smart Net Total Care Service, SP Base, Unified Computing Support Service, or Mission Critical Support Service contract for the designated products.

This Community will provide you with an overview about Cisco Smart Call Home features and how these features are embedded in a wide range of Cisco products to help your network. Smart Call Home provides higher network availability and support service quality.

Smart Call Home Portal Performance

On We are currently experiencing performance issues with accessing and operations of the Small Call Home portal. Users are being dropped from the portal. Our team is working to resolve this issue as quickly as possible. We apologize for any inconvenience this is creating.

Anil Dey Pillala

Smart call home : Nexus 5K SNMP


Please provide an insight into the SNMP command on NEXUS 5k for SCH  config.

cmd# snmp-server contact <sys-contact>

Please clarify on significance of the command and why is it used


Lawrence Searcy
Cisco Employee

Call Home in NX-OS and IOS use code outside the call home code base to create and send call home messages. One part of the code it uses is the SNMP MIB to store information required for call home messages.

The design goal of Call Home is to identify the person to contact, how to contact them, and where to send the RMA when Call Home sends in a message. It needs this information when building a call home message. It uses the following to do that:

    1. sysContact                          (Required in standard MIB)

    2. sysContactEmail                 (Required in Call-Home MIB)

    3. sysContactPhoneNumber   (Optional in Call-Home MIB)

But when Smart Call Home opens a TAC case due to a call home message being received, it actually uses the ID profile associated to the device to fill in these fields in the TAC case. But if you were going to automatically troubleshoot registration issues without a TAC case though, you would have to rely on the information in the Call Home message.

I'm not sure if the IOS call home code just doesn't verify that the sysContact exists before it starts functioning since it is set with a non call-home command [snmp-server contact], or IOS made sysContact optional. With Anonymous Smart Call Home, I can see where sysContact might be optional but so would sysContactEmail.

NX-OS requires and verifies that sysContact exists for Call Home to function.