01-15-2014 11:43 PM - edited 03-07-2019 05:36 PM
Hi,
I would like to disable this log massage:
an 16 07:35:15.714: CALL-HOME-DETAIL: Alert group 2 is valid(6)
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Checking if alert-group 3 is supported
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Alert group 3 is valid(6)
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Checking if alert-group 4 is supported
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Alert group 4 is valid(6)
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Checking if alert-group 5 is supported
Jan 16 07:35:15.714: CALL-HOME-DETAIL: Alert group 5 is valid(6)
Jan 16 07:35:15.714: CALL-HOME-DETAIL: unlock call home database sempahore
Jan 16 07:35:35.110: CALL-HOME-TRACE: Received event: 1
Jan 16 07:35:35.110: CALL-HOME-TRACE: Cleared rate limit counter
Jan 16 07:35:35.110: CALL-HOME-DETAIL:
httpc_enabled 1, status 0, sid 2
Jan 16 07:35:37.939: CALL-HOME-TRACE: show_call_home_summary_func() is called
Jan 16 07:35:37.939: CALL-HOME-TRACE: call_home_get_global_database() is entered
Jan 16 07:35:37.939: CALL-HOME-DETAIL: lock call home database semaphore
Jan 16 07:35:37.939: CALL-HOME-DETAIL: unlock call home database sempahore
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 0 is supported
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 0 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 0 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 0 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 1 is supported
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 1 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 1 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 1 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 2 is supported
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 2 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 2 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 2 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 3 is supported
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 3 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 3 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 3 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 4 is supported
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 4 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 4 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Alert group 4 is valid(6)
Jan 16 07:35:37.939: CALL-HOME-DETAIL: Checking if alert-group 5 is supported
Jan 16 07:35:37.939: CALL-HOME-TRACE: call_home_get_profile() is entered profile
Jan 16 07:35:37.939: CALL-HOME-DETAIL: lock call home database semaphore
Jan 16 07:35:37.939: CALL-HOME-DETAIL: unlock call home database sempahore
Jan 16 07:35:37.939: CALL-HOME-DETAIL: call_home_get_profile() found profile
I did:
no call-home
All configuration under call-home mode are set to default value. Cisco TAC profiles are deactivated and all other profiles are removed.
and disable all alert groups
But I am still receiving log massage.
Is there any way to disable them.
sh call-home
Current call home settings:
call home feature : disable
call home message's from address: Not yet set up
call home message's reply-to address: Not yet set up
vrf for call-home messages: Not yet set up
contact person's email address: Not yet set up
contact person's phone number: Not yet set up
street address: Not yet set up
customer ID: Not yet set up
contract ID: Not yet set up
site ID: Not yet set up
source ip address: Not yet set up
source interface: Not yet set up
Mail-server: Not yet set up
Rate-limit: 20 message(s) per minute
Available alert groups:
Keyword State Description
------------------------ ------- -------------------------------
configuration Disable configuration info
diagnostic Disable diagnostic info
environment Disable environmental info
inventory Disable inventory info
syslog Disable syslog info
Profiles:
Profile Name: CiscoTAC-1
Regards,
Ivan
Solved! Go to Solution.
06-17-2014 12:11 AM
workaround: I do not have this problem anymore, because I set the logging severity level debugging --> informational. (logging trap informational)
06-17-2014 12:11 AM
workaround: I do not have this problem anymore, because I set the logging severity level debugging --> informational. (logging trap informational)
06-19-2014 11:19 PM
thanks, it is working!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide