cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
31
Views
1
Helpful
1
Replies
Cisco Employee

NSO 4.1 - Best practice/guidelines for syslog configurations

 

Hi team,

 

 

Is there any best practice/guidelines in configuring the syslog forwarding from NSO to external syslog server ? What do we define for each facility local level ?

 

 

/ncs-config/logs/syslog-config/facility (daemon | authpriv | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | uint32) [daemon]

 

 

ncs.conf only allow option to include ncs.log, devel.log, netconf.log and snmp.log in syslog but not ncs-java-vm.log ?

 

Thanks

 

Best Regards,

 

BaoYi Chai

 

1 REPLY 1
Highlighted
Cisco Employee

Re: NSO 4.1 - Best practice/guidelines for syslog configurations

 

On 19/08/16 06:51, Bao Yi Chai (bchai) wrote:

 

> Hi team,

 

>

 

> Is there any best practice/guidelines in configuring the syslog

 

> forwarding from NSO to external syslog server ? What do we define for

 

> each facility local level ?

 

>

 

> /ncs-config/logs/syslog-config/facility (daemon | authpriv | local0 |

 

> local1 | local2 | local3 | local4 | local5 | local6 | local7 | uint32)

 

> [daemon]

 

>

 

 

 

I recommend the default here, i.e 'daemon'

 

 

 

> ncs.conf only allow option to include ncs.log, devel.log, netconf.log

 

> and snmp.log in syslog but not ncs-java-vm.log ?

 

>

 

 

The ncs-java-vm.log is by default all the stdout captured from the running jvm. If more advanced log handling is required for the JVM log, it's possible to

 

 

- turn off the stdout capture

 

 

- manually configure the log4j package which is typically

 

   used by all NSO Java code (including NEDs)

 

 

 

Using NSO itself to generate syslog from the Java log is not possible. (It would be very ugly too, where the Java multi line printouts would have to be massaged into unreadability)

 

 

 

/klacke