08-11-2009 01:55 AM - last edited on 02-11-2015 09:49 PM by Maiko-I
I have HP Network Automation 7.5 running on a linux machine.I know Network Automation works as a syslog server also but can somebody tell me in which folder does it save all the syslog logs of the devices?
P.S. This thread has been moevd from Network Management / (OpenView-NNM) Support and News Forum to Network Automation Support and News Forum. - Hp Forum Moderator
11-07-2009 10:44 PM
NAS uses the embedded Syslog server to store all information about devices, configuration and changes. Then NAS core server uses these logs to create reports. You can configure NAS log to store all logs remotely â that also called Syslog relay â
Points are welcomed
11-08-2009 10:36 PM
Thanks,how can I configure NAS to store syslog remotely?
Also I need to know if NAS stores all the running config of the devices in the DB(ms sql in my case)or in the application server?
If it is DB can you tell me in which table and in case of application server pl stell me in which folder?
04-04-2011 12:58 AM
I have the same requirement: i know, HP NA can be used as a Syslog relay, but I want to use it as local Syslog Server, but I don't know where syslog messages coming from devices are locally stored.
Could someone help me please ?
Thanks in advance.
07-24-2014 11:38 AM
I know that this threat might be old, but as I was looking for the same thing,
here are my conclusions, that I grave in another threat:
- The way to check the syslog information that NA is retreiving are 2:
1) With a Wireshark or tcpdump, for Win and Linux.
2) With the Troubleshooting tool:
- Go to: Admin -> Troubleshooting:
- Highlight the following in "Enabling logging for":
And I add the following options as weel:
"At level" -> Trace (most messages)
This will fill a file set on : /opt/NA/server/log/syslog_wrapper.log
Normally, this file do not have much activities, but, remember that adding this "trace messages"
will full it, and it is not something to be done permanently. it is just for test/review actions,
and the settings in the trobleshooting tool must set to normal in a short period of time.
Hope this help!