From what I understand the netflow would need to source from the root routing instances and not a logical system directly. So here is a theory that would need to be tested.
Since your destination server is connected to the logical system, you might be able to create a logical tunnel pair that connect this logical system to the root routing instance.
Then be create a route for the destination address of that server in the root routing instance pointed across this logical tunnel pair.
And have a return route for source address of the netflow in the logical system also pointed back down that pair to complete the communication path.
Depending on what else is accessible in the root routing instance you might need some security precautions installed as well.
Documentation on creating a logical tunnel pair interface pair in logical systems.
https://www.juniper.net/documentation/us/en/software/junos/interfaces-encryption/topics/topic-map/connecting-logical-systems-logical-tunnel-interfaces.html
------------------------------
Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
http://puluka.com/home------------------------------
Original Message:
Sent: 03-17-2025 07:42
From: Jayvee Sagarino
Subject: Netflow in Logical Systems for MX204
Hi,
Did anyone here successfully configured a netflow monitoring for a logical systems for mx204?
I found an unofficial article that it is not supported. If that turns out to be true, is there an alternative?
Thank you
------------------------------
Jayvee Sagarino
------------------------------