[j-nsp] system syslog host in another routing instance

[Mark Menzies]

Hit this issue when logging to STRM for SRX data plane traffic

Have a look at this for more details;
http://kb.juniper.net/InfoCenter/index?page=content&id=KB22692


Seems that the initial packet originates in inet.0 even when we have a
specific source address to send the traffic from.  We need to route the
traffic to the correct routing instance for it to work

HTH


On 19 December 2012 10:51, Uriel Segal <URIEL at bynet.co.il> wrote:

> Due to SYSLOG's UDP/one-way nature, you can add a static route in the
> global routing-table, route destination 10.14.140.125/32 to next-table
> YYYYYYYY.inet.0
>
> This will do the job
>
> BR,
> Uriel
>
>
>
> Colleagues,
>
> It seems possible to send SNMP traps to a host in a non-default routing
> instance, like this:
>
> snmp {
>     community XXXXXXXX {
>         routing-instance YYYYYYYY {
>             }
>         }
>     }
>
> Is it possible to send syslog messages to a host in a non-default routing
> instance? I can ping this host like this:
> ping 10.14.140.125 routing-instance YYYYYYYY
>
> Running JUNOS 10.4R8.5 on an M120.
>
> Thank you in advance for any input:
>
> --
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> sip:sudakov at sibptus.tomsk.ru
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>