Is it appropriate, <>, to Tee unidirectional Syslog UDP packets to two recipient servers by sending the packets to an RB133 as the primary address & then forwarding the packets to two destinations?
RouterOS would have to generate more than one packet for each one being routed, which I don’t think is possible… if it’s for routerOS logging, you can possibly setup 2 logging rules, one to each syslog box ?
I thought about adding a bridge with a few fake interfaces, and then natting from each, but I’m not sure it’s going to work as you need.
The syslog packets are from embedded boxes. They generate a lot of Syslog data and so I am not able to duplicate the packets at the source as it will occupy too much CPU time.
At worst case I was looking at a script on the ROSbox which looks for a dead server & then redirects accordingly. It would be cleaner/easier if I could send to both servers at all times hence the request.
At this stage I’ll settle for any ideas which might do either 
Cheers
Don