Yes, that is what I'm doing:
inet.0: 886098 destinations, 1228703 routes (886098 active, 0 holddown, 23 hidden)
+ = Active Route, - = Last Active, * = Both
10.x.y.z/32 *[Static/5] 2w0d 21:11:57
to table mgmt_junos.inet.0
(I think I can share the 1st octect of the sflow server address without requiring an NDA :-)
------------------------------
BEN BIGGIE
------------------------------
Original Message:
Sent: 04-05-2022 18:19
From: QURAITUL AIN
Subject: sflow mx204 mgmt_junos
Wouldnt it the other way round tho ? Should you be leaking the sflow server subnet which is FXPO living in junos_mgmt into inet ?
------------------------------
QURAITUL AIN
Original Message:
Sent: 03-18-2022 20:40
From: Unknown User
Subject: sflow mx204 mgmt_junos
I got this working finally. Tried RIB-groups, instance-import and neither seem to work with mgmt.junos.inet.0. I ended up using a next-table static route:
set routing-instances mgmt_junos routing-options static route <sFlowServerSubnet> next-table inet.0
Only caveat is that you can't leak a route from mgmt.junos.inet.0 into inet.0 or it will cause a loop.
Original Message:
Sent: 03-10-2022 10:32
From: Unknown User
Subject: sflow mx204 mgmt_junos
I'm trying to do the same thing on an MX by leaking the sFlow subnet route from inet.0 to the mgmt.junos.inet.0 VR with an import RIB-group. However, I keep getting error that I need to create the mgmt.junos routing-instance again. This may be a limitation of using RIB-groups with the management RI. Going to look at FBF and any other methods to accomplish this.
Original Message:
Sent: 03-08-2022 10:53
From: BEN BIGGIE
Subject: sflow mx204 mgmt_junos
Hi
I've been trying to get sflow going (unsuccesssfully for a while now on our mx204s.
I would really like to be able to stream from my fxp0 interfaces which is within an mgmt_junos vrf.
For the purposes of RPKI I can set up a peering session by importing my loopback interface route into mgmt_junos and the route to the RPKI validator into main (via instance-import referencing policy statements)
But importing the sflow collector address into main doesn't seem to work.
Any suggestions? Or is it is that I can only source sflow from an address on my fpc and out of an fpc interface?
Thanks in advance,
Ben
------------------------------
BEN BIGGIE
------------------------------