Unable to send traffic logs to Juniper Security Director (On Prem) when the outgoing interface is in a routing instance 

By default, Juniper Security Director (On Prem) will push below config when security log is configured.

You may run the below cmd to verify the connectivity

• If the SD is reachable from default routing-instance then below test will succeed.

labroot@vsrx> telnet 10.x.x.x port 6514             

Trying 10.x.x.x...

• If the source-interfface used to forward logs is in a custom routing-instance then below test will succeed.

labroot@vsrx> telnet 10.x.x.x port 6514  routing-instance ROU_INSTANCE-1           

Trying 10.x.x.x...

Connected to 10.x.x.x

Escape character is '^]'.

When the source-interface used is attached to an routing

set security log mode stream
set security log format sd-syslog
set security log source-interface ge-0/0/0.0
set security log stream sd-logs category all
set security log stream sd-logs host 10.x.x.x
set security log stream sd-logs host port 6514
set security log stream sd-logs transport division line-based
set security log stream sd-logs transport protocol tls
set security log stream sd-logs transport tls-profile syslog-profile

-instance other than default instance then you need to use below cmd so that SRX will use different routing instance to forward logs.

• set security log stream sd-logs host 10.219.87.178 routing-instance ROU_INSTANCE-1

2025-08-07 : Article Created

2025-09-24: Removed IPs, changed visibility