Forum Discussion
Stefan_Klotz_85
Cirrus
CirrussFlow and Route Domains
Hi there,
I'm aware that sFlow traffic is not possible via the mgmt-interface. That's fine in general, but we have one cluster using Route Domains. The Common Route Domain is only be used with an access VLAN (point-2-point Connection between the two LB cluster-nodes, no other L3 device in that VLAN) for heartbeat and sync traffic. It's intended to route sFlow traffic via a transfer VLAN in Route Domain 1. Is this possible at all and if yes, how? Or can I easily configure the sFlow Receiver in the context of Route Domain 1 (didn't try this so far)? Or do we have to re-think our sFlow design? Thanks for your help!
Ciao Stefan :)
Andy_McGrathCumulonimbus
I have not ever tested this but my guess would be that as long as the Route Domain where you are capturing/sampling traffic can route to the sFlow Receiver than should not have a problem.
So if the egress for the sFlow Receiver is on a different Route Domain than the VLAN being captured/sampled you would need to have a Strict Isolation is disabled and the Route Domains are configured as parent/child.
Stefan_Klotz_85Ok, I configured now a sFlow Receiver in each Route Domain and there is also a default route available in each Route Domain. But I still don't see any outgoing packets with tcpdump. Or is sFlow only working in the Common Route Domain?
So how do I need to configure the sFlow Receiver and maybe the Route Domains to get this working?
Thank you!
Ciao Stefan :)
- Stefan_Klotz_85
Although our Common Route Domain is only used/configured with the heartbeat-VLAN, I setup the sFlow stuff there as well together with a default route pointing to the neighbor LB via the heartbeat-VLAN. Once done, I can see UDP packets with tcpdump. So does this mean sFlow is only working in the Common Route Domain? Or how do I need to adjust the setup to get this working? There is no real documentation on how sFlow is working with Route Domains. Thank you!
Ciao Stefan :)