Preview Tool

Cisco Bug: CSCte70856 - callhome stops sending alerts, copy running start may fail

Last Modified

May 23, 2018

Products (1)

  • Cisco MDS 9000 Series Multilayer Switches

Known Affected Releases

4.2(7a) 5.0(1)

Description (partial)

The Cisco SAN-OS callhome feature stops sending any callhome alerts.

In extreme cases, the callhome feature may become unconfigurable and the configuration undisplayable and unsaveable. The following type of messages may be seen:

  <CmdBold>show running-config<noCmdBold>
  Ascii cfg send notify failed: Device or resource busy

The following type of syslog messages may be logged about destination sap '66' and opcode '4853':

  %KERN-2-SYSTEM_MSG: mts_print_longest_queue_state: opcode counts for first and last 50 messages in pers_q of sap 66: - kernel
  %KERN-2-SYSTEM_MSG: mts_print_msg_opcode_in_queue:  opcode 4853 - 100 messages - kernel
  %KERN-2-SYSTEM_MSG: mts_acquire_q_space() failing - no space in dst sap 66, uuid 63, src sap 28, opcode 4853 - kernel

This issue occurs when alerting priority configured in a callhome profile is higher than the level of the incoming alerts (eg, rmon alerts sent from the port monitor feature).
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.