04-18-2012 07:23 AM
After we upgraded from 3.3(1c) to 5.2(2) our Call Home has stopped sending emails when any host logs out/into any of the switches. Nothing else has changed, the same profles exist with the same “MsgLevel” settings.
In the release notes for 4.2(1b) it states; “In MDS NX-OS Release 4.2(1b), CFS cannot distribute the following Call Home commands that can be
configured with the destination-profile command:
• destination-profile profile_name transport-method
• destination-profile profile_name http”
That does not show up when we run “sh running-config callhome”.
We can still run a Test or Inventory without any issues and we receive the emails.
Thanks
Solved! Go to Solution.
04-19-2012 08:04 AM
Hi,
The interface with logging level 5 is probably a port-channel.
You can look at the raw output of the command to be sure.
Since you can't | to (5), you can capture the output to a file, then search the text file.
Regards,
David.
04-18-2012 07:37 AM
Hi,
The upgrade got you a new knob to change the syslog level for link failures.
For syslogPortGrup to callhome the syslog level needs to be critical.
Is this what you are looking for?
config
logging level port link-failure crit
My callhome test worked with this config.
callhome
email-contact sysadmin@cisco.com.com
phone-contact +1-800-555-5555
streetaddress 123 Main Street, USA
destination-profile full_txt email-addr test@cisco.com
destination-profile short_txt email-addr test@cisco.com
destination-profile xml email-addr test@cisco.com
no destination-profile full_txt alert-group all
destination-profile full_txt alert-group RMON
no destination-profile short_txt alert-group all
destination-profile short_txt alert-group RMON
destination-profile full_txt alert-group test
destination-profile short_txt alert-group test
no destination-profile xml alert-group all
transport email from switchname@db.com
transport email reply-to no-reply@db.com
transport email smtp-server a.b.c.d port 25
enable
exit
Regards,
David
04-19-2012 06:22 AM
Did the change but when I run "sh logg level port" afterwards it was the same as before? Still at 5 (Notifi).
Facility Default Severity Current Session Severity
-------- ---------------- ------------------------
port 5 5
0(emergencies) 1(alerts) 2(critical)
3(errors) 4(warnings) 5(notifications)
6(information) 7(debugging)
04-19-2012 06:36 AM
HI,
Thanks for the feedback.
I need to research or open a new bug for 'port link-failure' not listed in the output of 'show logging level'.
Check the output of ...
9513-2(config)# show port internal info all | i syslog
Global link failure syslog level = 2 <------ global level
Link failure syslog level (5) <----- interface level
The workaround for ....
CSCti92353 IF_DOWN_LINK_FAILURE_CRIT not generated
... is ..
After upgrading to a release with the fix you will need to reconfigure the link-failure logging level to activate the fix.
Config
no logging level port link-failure crit
logging level port link-failure crit
9513-2(config)# no logging level port link-fail crit
From my lab switch...
9513-2(config)# show port internal info all | i syslog
Global link failure syslog level = 2 <------ global level
Link failure syslog level (5) <----- interface level
Link failure syslog level (5)
Link failure syslog level (5)
Link failure syslog level (5)
9513-2(config)# no logging level port link-fail crit
9513-2(config)# logging level port link-fail crit
9513-2(config)# show port internal info all | i syslog
Global link failure syslog level = 2
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Regards,
David
04-19-2012 07:47 AM
Strange, all of them say 2 except for one of them three from the bottom? I will wait for the email to arrive.
Global link failure syslog level = 2
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (2)
Link failure syslog level (5)
Link failure syslog level (2)
Link failure syslog level (2)
Thanks
04-19-2012 08:04 AM
Hi,
The interface with logging level 5 is probably a port-channel.
You can look at the raw output of the command to be sure.
Since you can't | to (5), you can capture the output to a file, then search the text file.
Regards,
David.
04-20-2012 08:22 AM
That did fix the problem but the emails are much bigger than before, shows lots of the last logouts/logins. Might be "show logging logfile | tail -n 200" that shows up in the email.
Thanks
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