Sponsored Content
Full Discussion: Centralized syslog server
Top Forums UNIX for Advanced & Expert Users Centralized syslog server Post 302082037 by getwithrob on Sunday 30th of July 2006 05:56:18 PM
Old 07-30-2006
Centralized syslog server

I have a syslog server running Solaris 5.9 that is used exclusively to receive log messages from several thousand Cisco devices. The syslog server is and has been running fine for several months..

I would like to take all messages logged from the Cisco devices on this server and forward them to another "Centralized" logging server. From what I've been able to find, this is done quiet often and is referred to as a Centralized syslog server.

Please see the attached /etc/syslog.conf file from the box that's working today. The messages from the Cisco devices are written to the /var/log/rtrlog file as shown 2 lines from the bottom of the file. Again, this works today. Please look at the last line which I would like to add that will forward these messages to another syslog server w/ an IP address of 10.10.10.10 (example address).

Will this work?

Thank in advance for any input...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What are people using for Centralized Unix Administration

What are people using for Centralized Unix Administration? I'm not just talking user administration, I'm also talking system administration. I prefer a customized SSH enivonment that allows me to connect to server after server quickly to perform multiple tasks at once. I know there are products... (0 Replies)
Discussion started by: x96riley3
0 Replies

2. Solaris

How to implement Centralized logging server

Hi, I have Sun One Application server installed on 2 Solaris servers. Currently I am getting their logs in relative server. I am using log4j for logging. Now I want to change this. I want such that I should get both S1AS's log on third server with log4j. How can I do that ? I got one idea... (0 Replies)
Discussion started by: neel.gurjar
0 Replies

3. UNIX for Dummies Questions & Answers

centralized unix user management

Does it exist centralized tools on unix for managing users of all servers (like windows AD) ? (1 Reply)
Discussion started by: astjen
1 Replies

4. UNIX for Dummies Questions & Answers

how to configure centralized log server

hi, i am beginner i am using small lan setup all machine fc 6 and fc7 8 and fedora 9 also i want to know how to configure centralized log server on fedora 9 step by step any one help me Thanks (0 Replies)
Discussion started by: poswer
0 Replies

5. UNIX for Advanced & Expert Users

Multi-platform Centralized Patch Management

We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies

6. UNIX for Advanced & Expert Users

Need help on setting up Centralized Server

Hello All, I am working on SuSe Linux Platform. Some times ago i got an issue with an application for which i had to update that in all desktops (SLED == SuSe Linux Desktop). Since this time number of desktops were less then it was possible to go and update package manually. But in... (1 Reply)
Discussion started by: shirsha
1 Replies

7. AIX

Centralized RBAC using Active Directory or (AD LDS)

Hi everybody, I am working on the RBAC implementation on AIX 6.1 servers. There are quite a few servers and I would like the RBAC objects to be stored centrally in a LDAP database. It would be easier from the administration point of view. Has anyone ever been able to use Active Directory or... (1 Reply)
Discussion started by: romiban
1 Replies

8. Infrastructure Monitoring

Centralized linux system log analyzer?!

Hello everyone! I`m searching for linux log parser application. I already find some ways, but the best looks logzilla. Requirements: Web interface for viewing Filtering in web Notifications in web or email Open source Support linux system logs, custom logs and apache logs. I will... (5 Replies)
Discussion started by: jabalv
5 Replies

9. Solaris

Configuring Centralized Solaris Server to Receive Syslogs

Hello, I am new to Solaris. However, I was able to configure the Syslog server on Solaris. I am using a windows client to send logs to my Solaris syslog server. this is working fine. however, I have 23 servers which are sending their logs to the syslog server and it is very difficult to read all... (2 Replies)
Discussion started by: ravmohun
2 Replies
syslog.conf(4)							   File Formats 						    syslog.conf(4)

NAME
syslog.conf - configuration file for syslogd system log daemon SYNOPSIS
/etc/syslog.conf DESCRIPTION
The file /etc/syslog.conf contains information used by the system log daemon, syslogd(1M), to forward a system message to appropriate log files and/or users. syslogd preprocesses this file through m4(1) to obtain the correct information for certain log files, defining LOGHOST if the address of "loghost" is the same as one of the addresses of the host that is running syslogd. A configuration entry is composed of two TAB-separated fields: selector action The selector field contains a semicolon-separated list of priority specifications of the form: facility.level [ ; facility.level ] where facility is a system facility, or comma-separated list of facilities, and level is an indication of the severity of the condition being logged. Recognized values for facility include: user Messages generated by user processes. This is the default priority for messages from programs or facilities not listed in this file. kern Messages generated by the kernel. mail The mail system. daemon System daemons, such as in.ftpd(1M) auth The authorization system: login(1), su(1M), getty(1M), among others. lpr The line printer spooling system: lpr(1B), lpc(1B), among others. news Designated for the USENET network news system. uucp Designated for the UUCP system; it does not currently use the syslog mechanism. cron Designated for cron/at messages generated by systems that do logging through syslog. The current version of the Solaris Operat- ing Environment does not use this facility for logging. audit Designated for audit messages generated by systems that audit by means of syslog. local0-7 Designated for local use. mark For timestamp messages produced internally by syslogd. * An asterisk indicates all facilities except for the mark facility. Recognized values for level are (in descending order of severity): emerg For panic conditions that would normally be broadcast to all users. alert For conditions that should be corrected immediately, such as a corrupted system database. crit For warnings about critical conditions, such as hard device errors. err For other errors. warning For warning messages. notice For conditions that are not error conditions, but may require special handling. A configuration entry with a level value of notice must appear on a separate line. info Informational messages. debug For messages that are normally used only when debugging a program. none Do not send messages from the indicated facility to the selected file. For example, a selector of *.debug;mail.none sends all messages except mail messages to the selected file. For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a level of crit also logs messages at the alert and emerg levels. The action field indicates where to forward the message. Values for this field can have one of four forms: o A filename, beginning with a leading slash, which indicates that messages specified by the selector are to be written to the specified file. The file is opened in append mode if it exists. If the file does not exist, logging silently fails for this action. o The name of a remote host, prefixed with an @, as with: @server, which indicates that messages specified by the selector are to be forwarded to the syslogd on the named host. The hostname "loghost" is treated, in the default syslog.conf, as the hostname given to the machine that logs syslogd messages. Every machine is "loghost" by default, per the hosts database. It is also pos- sible to specify one machine on a network to be "loghost" by, literally, naming the machine "loghost". If the local machine is designated to be "loghost", then syslogd messages are written to the appropriate files. Otherwise, they are sent to the machine "loghost" on the network. o A comma-separated list of usernames, which indicates that messages specified by the selector are to be written to the named users if they are logged in. o An asterisk, which indicates that messages specified by the selector are to be written to all logged-in users. Blank lines are ignored. Lines for which the first nonwhite character is a '#' are treated as comments. EXAMPLES
Example 1 A Sample Configuration File With the following configuration file: *.notice /var/log/notice mail.info /var/log/notice *.crit /var/log/critical kern,mark.debug /dev/console kern.err @server *.emerg * *.alert root,operator *.alert;auth.warning /var/log/auth syslogd(1M) logs all mail system messages except debug messages and all notice (or higher) messages into a file named /var/log/notice. It logs all critical messages into /var/log/critical, and all kernel messages and 20-minute marks onto the system console. Kernel messages of err (error) severity or higher are forwarded to the machine named server. Emergency messages are forwarded to all users. The users root and operator are informed of any alert messages. All messages from the authorization system of warning level or higher are logged in the file /var/log/auth. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
at(1), crontab(1), logger(1), login(1), lp(1), lpc(1B), lpr(1B), m4(1), cron(1M), getty(1M), in.ftpd(1M), su(1M), syslogd(1M), syslog(3C), hosts(4), attributes(5) SunOS 5.11 26 Apr 2006 syslog.conf(4)
All times are GMT -4. The time now is 09:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy