01-09-2017 11:58 PM - edited 03-01-2019 05:07 AM
Hi,
APIC running version : 2.1(1h)
I have followed the LAB described below
My configuration seems to be correct but unfortunately I'm receiving email from the Apic with an empty body and a blank subject.
(Format short-txt and xml)
Did you already have this kind of issue ?
How can I check easily the callhome config and see the statistics ?
Is there any way on the Apic to capture Smtp traffic on the oobmgmt ?
Thank you (Again ;-).
Ju
Solved! Go to Solution.
01-13-2017 06:51 AM
Ju,
What versions are you running on your APIC & Leaf\Spine nodes?
I used your setup in my lab and it works as expected.
The fact that you are receiving an email from the APIC indicates the configuration is configured correct or at least partially.
Can you send me the text output of the long message display of the email message?
Also, try removing the monitoring policies for Callhome under "Fabric Policies - DEFAULT" and "Access Policies - DEFAULT". Then, configure "Fabric Policies - COMMON" only for callhome and your callhome destination group.
and retest.
Thanks
T.
01-11-2017 03:41 AM
Hi Ju,
The minimum configuration needed to test CallHome is:
CallHome Desintation Group with CallHome Destination
CallHome Source defined under either Fabric or Access Policies
Configuring Scheduler is only required when configuring CallHome Inventory
CallHome messages are sent mostly from APIC2 when the APIC cluster size is 3; we can verify if CallHome is sending emails by running tcpdump on the appropriate interface of the devices.
After reviewing the tcpdump outputs, we can confirm whether or not the device is sending out the CallHome emails.
If we see traffic being sent by the interface, we can also review the svc_ifc_eventmgr.bin.log.stderr file for the output of the sessions with the SMTP server.
CallHome logs are located in the device that is sending the CallHome emails under the svc_ifc_eventmgr.bin.log file.
Log Locations (assuming APIC2 is sending the CallHome emails):
In the log file of the TechSupport for APIC2, the log can be found under /data/log/.
In a live environment, the log can be found in APIC2 under /var/log/dme/log/.
HTH
Manish
01-13-2017 06:10 AM
01-13-2017 06:51 AM
Ju,
What versions are you running on your APIC & Leaf\Spine nodes?
I used your setup in my lab and it works as expected.
The fact that you are receiving an email from the APIC indicates the configuration is configured correct or at least partially.
Can you send me the text output of the long message display of the email message?
Also, try removing the monitoring policies for Callhome under "Fabric Policies - DEFAULT" and "Access Policies - DEFAULT". Then, configure "Fabric Policies - COMMON" only for callhome and your callhome destination group.
and retest.
Thanks
T.
01-13-2017 07:12 AM
Hi Thomas,
I'm running 2.1(1h) and n9000-12.1(1h)
You are right. The header coming from the long message display is correct :
Reply-To: <juma@monserver.frTo: juma@monserver.frFrom: juma@monserver.frSubject: Node 104 is inactive and not reachable.ContentType: plain/textCreated: 1484312328173Description: Node 104 is inactive and not reachable.topology/pod-1/node-104/fault-F1543Status: raised_clearingSeverity: critical>
To: Undisclosed recipients:;
Return-Path: juma@monserver.fr
MIME-Version: 1.0
Content-Type: text/plain
X-MS-Exchange-Organization-Network-Message-Id: ffb48910-1fd6-4843-4c5a-08d43bb91cef
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: w15000100d3ex9.monserver.local
X-MS-Exchange-Organization-AuthAs: Anonymous
Probably a security parameter in my outlook client.
Thank you for your help.
Regards
Ju
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