topic Re: ISE troubleshooting with CLI and log files in Network Access Control https://community.cisco.com/t5/network-access-control/ise-troubleshooting-with-cli-and-log-files/m-p/3549079#M530522 <HTML><HEAD></HEAD><BODY><P>If your customers are experiencing these issues, it's best to open TAC cases. The reports, live logs, and log sessions are what for customers whereas the debug logs are mainly for TAC, etc. If customers preferring to troubleshoot themselves, then the debug log file names imply the areas they are for. Often, we would need to cross reference multiple debug log files from different nodes so TAC assistance is preferred.</P></BODY></HTML> Fri, 31 Mar 2017 03:17:55 GMT hslai 2017-03-31T03:17:55Z ISE troubleshooting with CLI and log files https://community.cisco.com/t5/network-access-control/ise-troubleshooting-with-cli-and-log-files/m-p/3549078#M530520 <HTML><HEAD></HEAD><BODY><P>Hi All,</P><P></P><P>I'm looking for some assistance please. I'm struggling to find a table which details what each log file's purpose is on the CLI. For example:</P><P>What log files must I look at to troubleshoot active directory issues?</P><P>What log files must I look at to troubleshoot replication issues across the ISE deployment?</P><P>What log files must I look at to troubleshoot patch upgrade status on a particular node?</P><P></P><P>I'm looking for something like this:</P><P></P><TABLE border="0" cellpadding="0" cellspacing="0"><TBODY><TR><TD style="border: solid windowtext 1.0pt; padding: 0 5.4pt 0 5.4pt;" valign="top" width="131"><P><STRONG>Log file name</STRONG></P></TD><TD style="border: solid windowtext 1.0pt; border-left: none; padding: 0 5.4pt 0 5.4pt;" valign="top" width="570"><P><STRONG>Function/purpose</STRONG></P></TD></TR><TR><TD style="border: solid windowtext 1.0pt; border-top: none; padding: 0 5.4pt 0 5.4pt;" valign="top" width="131"><P>replication.log</P></TD><TD style="border-top: none; border-left: none; border-bottom: solid windowtext 1.0pt; border-right: solid windowtext 1.0pt; padding: 0 5.4pt 0 5.4pt;" valign="top" width="570"><P>All replication status/updates that happen throughout the ISE deployment and any errors that might occur.</P></TD></TR></TBODY></TABLE><P></P><P>This information would need to cover both system and application based logs.</P><P></P><P>Can someone point me in the right direction please?</P><P></P><P>Thanks!</P><P>Nolan</P></BODY></HTML> Mon, 27 Mar 2017 17:47:48 GMT https://community.cisco.com/t5/network-access-control/ise-troubleshooting-with-cli-and-log-files/m-p/3549078#M530520 nolanrumble 2017-03-27T17:47:48Z Re: ISE troubleshooting with CLI and log files https://community.cisco.com/t5/network-access-control/ise-troubleshooting-with-cli-and-log-files/m-p/3549079#M530522 <HTML><HEAD></HEAD><BODY><P>If your customers are experiencing these issues, it's best to open TAC cases. The reports, live logs, and log sessions are what for customers whereas the debug logs are mainly for TAC, etc. If customers preferring to troubleshoot themselves, then the debug log file names imply the areas they are for. Often, we would need to cross reference multiple debug log files from different nodes so TAC assistance is preferred.</P></BODY></HTML> Fri, 31 Mar 2017 03:17:55 GMT https://community.cisco.com/t5/network-access-control/ise-troubleshooting-with-cli-and-log-files/m-p/3549079#M530522 hslai 2017-03-31T03:17:55Z