aarseniev wrote:The basic syslog config from the MX (from memory so if syntax is a bit off sorry):
set system syslog host 192.168.2.2 any any
NOTE: there is also file syslog setup but they seem to work
You are sending the MX syslog to SRX itself, not to STRM.
If You change 192.168.2.2 to actual STRM IP _AND_ make sure MX know a route to actual STRM IP, then You should see the MX syslog arriving at STRM.
HTH
Thx
Alex
Alex you are correct. I have a routing instance created in the SRX that takes all the syslog from all the devices in my network and routes it to the STRM. I'm quite confident that if the syslog message would get to the SRX, that it would be routed properly. Also trying to create a route in the MX to let it know how to get to the STRM on the ..255 network, would require it to go to the SRX anyway as there is no direct connection between the two networks.
The fact that I do not see any packets hitting the interface leaving the MX is the issue and having the separate 172/30 network between the MX and SRX requires that no matter what, the message needs to go through the SRX to get to the STRM on the x.x.255 network.
I'm guessing that it's the OPERATION NOT PERMITTED error when I try to ping out the interface from the MX to the SRX that I need to resolve but I don't know how. I'm thinking that if I get that solved, the packet would at least leave the MX and then it's just a routing issue.