Yes we've experienced that...4.8.0, inband setup. We aren't sure why it stops, but unlike your case, ours survives the "kick all users". To get it going again, we navigate to the syslog setup in the CAM and hit "update", then it starts again. We think it could be related to the CAM trying to write to the syslog and if for any reason it cannot (e.g., a permissions issue), the syslogging stops.
-Aaron On Tue, Oct 5, 2010 at 10:00 AM, David Pifer <[email protected]>wrote: > Has anyone else encountered SYSLOG services from the CAM just stopping? It > appears to happen when we have our weekly “Kick All Users” moment or the > periodic system status message will cause it to stop too… I can open a TAC > case but I wanted to ask someone else before I burn the case. > > > > > > David L. Pifer - N9YNF - CCNA > > TIS Network Engineering Services > Indiana State University, Office of Information Technology > 210 N. 7th St., Rankin Hall R044, Terre Haute, IN 47809 > 812.237.2923 office 812.237.4361 fax > > [image: Description: Description: CCNA] > > * * > > *Indiana State University and the Office of Information Technology would > like for you to know: > *** > This email, and any attachments, thereto, is intended only for use by the > addressee(s) named* > > *herein and may contain privileged and/or confidential information. If > you are not the intended* > > *recipient of this email, you are hereby notified that any dissemination, > distribution or copying of* > > *this email, and any attachments thereto, is strictly prohibited. > *** > A full disclosure of ISU and OIT Official Computing Policies and Procedures > is available at* > > *http://www.indstate.edu/oit/official_docs/compolicy.html<http://web.indstate.edu/oit/official_docs/compolicy.html> > *** * > > > -- Aaron Abitia Network Analyst Network Administration, ITS Cal Poly State University Tel: 805.756.1295
<<image001.jpg>>
