Routing

Hello!

We have EX3300 and 3400 switches that are connected to our ISP, we have a routing-instance to our server network (172.x.x.x) and i would like for the switches to send syslog messages to a host in that network.

But as of now i cant seem to specify wich Routing-Instance the system syslog should use.

I've tried source-address but that doesnt work either, is there a way to specify wich routing-instance system syslog messages should use?

user * {
any emergency;
}
host 172.X.X.X/32 {
any info;
source-address 10.10.10.10;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}

Trying adding this

set system syslog server routing-instances <> 

Hi Mhu!

Thanks for your reply, that requires for the app-engine to be configured.

And I wonder if it should be required for an eslog host listening for syslog messages from the Juniper switches, the issue is there is only an route to the server network via our routing-instance.

Regards
Andreas

You can try to leak the route from routing-instance to main instance so that syslog server is reachable from main isntance.

If you can share the "show route" for destination ip (syslog server ip) and source ip (local source ip) I can try to help with required configuration.

Thanks

Vishal

Hi!

I've added the static route to the routing-instance.

{master:1}
root@SW01> show route 172.16.8.10

inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.16.8.10/32 *[Static/5] 00:55:10
to table 901-Data.inet.0

901-Data.inet.0: 214 destinations, 214 routes (214 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 5w4d 05:44:27, metric 100, tag 3301
> to 10.99.92.41 via irb.911

902-Voip.inet.0: 21 destinations, 21 routes (21 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 5w4d 05:44:25, metric 100, tag 3301
> to 10.99.94.41 via irb.912

{master:1}
root@SW01> show route 172.16.8.10 source-gateway 10.99.99.40

inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

901-Data.inet.0: 214 destinations, 214 routes (214 active, 0 holddown, 0 hidden)

902-Voip.inet.0: 21 destinations, 21 routes (21 active, 0 holddown, 0 hidden)

It seems like it should be fine now but im not recieving any messages.

Hi,

When you ping from the device do you see the ICMP request messages on the server?

Hi Vishal,

As follows, Dest IP:

{master:1}
root@-SW01> show route 172.16.8.81 (IP of server)

901-Data.inet.0: 239 destinations, 239 routes (239 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 2d 08:53:38, metric 100, tag 3301
> to 10.99.93.49 via irb.911 (for ath clients/data traffic)

902-Voip.inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 2d 08:53:38, metric 100, tag 3301
> to 10.99.95.49 via irb.912 (For un-auth clients)

{master:1}
root@XXX-SW01> show route 172.17.60.254 (Source)

901-Data.inet.0: 239 destinations, 239 routes (239 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.17.60.254/32 *[Local/0] 4d 18:52:21
Local via irb.101

902-Voip.inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 2d 09:02:20, metric 100, tag 3301
> to 10.99.95.49 via irb.912

Is there anything missing you would like to know?

Thanks in advance

Found the information you are looking for 

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/routing-instance-edit-system-syslog.html

This is supported from 18.4 above. Before 18.4, you need to play some tricks with the route as mentioned above 

Thanks!

I'l make sure to review the updates, we are a few versions behind currently.

Hi,

You can add a static route for the syslog server in the main instance to point to the routing-instance via which the server is rechable for the look up.

Example:

set routing-options static route 172.X.X.X/32 next-table <routing-instance>.inet.0

Let us know if the above helps or not.

Could you please check this KB article for this issue.

https://kb.juniper.net/InfoCenter/index?page=content&id=KB34199