Mailing List Archive

Interface Views with Dynamic Flow Collection Interfaces
Is there anyway to use the Interface Views feature while also using the
Dynamic Flow Collection Interfaces feature based on Probe IP Address?

Example:
We export flows from 10 different routers (edge01/edge02) in 5 different
datacenters. I'd like a interface view for Datacenter1 to include its
edge01 and edge02 routers.

Even if I have to know the Probe IP address in advanced and specify it on
cmd line, that is fine but the dynamic interfaces are not named what I
think the Interface Views feature would expect or reference.

Thanks,
Ryan
Re: Interface Views with Dynamic Flow Collection Interfaces [ In reply to ]
Hi Ryan,


> On 21 Jul 2017, at 18:38, Ryan Gelobter <ryan.g@atwgpc.net> wrote:
>
> Is there anyway to use the Interface Views feature while also using the Dynamic Flow Collection Interfaces feature based on Probe IP Address?
>

Currently, this is not supported. However, you can do the following:

instruct your Datacenter1 edge01 and edge02 routers to export flows also to another instance of nprobe listening on a different port.

Then start that nprobe (but this time don't use the %EXPORTER_IPV4_ADDRESS in the template) and use zmq with another endpoint, say tcp://*:5557 <tcp://*:5557>

Finally, start your ntopng with an extra interface that collects data from the latter endpoint with -i tcp://127.0.0.1:5557 <tcp://127.0.0.1:5557>

Regards,
Simone



> Example:
> We export flows from 10 different routers (edge01/edge02) in 5 different datacenters. I'd like a interface view for Datacenter1 to include its edge01 and edge02 routers.
>
> Even if I have to know the Probe IP address in advanced and specify it on cmd line, that is fine but the dynamic interfaces are not named what I think the Interface Views feature would expect or reference.
>
> Thanks,
> Ryan
> _______________________________________________
> Ntop mailing list
> Ntop@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop
Re: Interface Views with Dynamic Flow Collection Interfaces [ In reply to ]
Hi Ryan,


> On 21 Jul 2017, at 18:38, Ryan Gelobter <ryan.g@atwgpc.net> wrote:
>
> Is there anyway to use the Interface Views feature while also using the Dynamic Flow Collection Interfaces feature based on Probe IP Address?
>

Currently, this is not supported. However, you can do the following:

instruct your Datacenter1 edge01 and edge02 routers to export flows also to another instance of nprobe listening on a different port.

Then start that nprobe (but this time don't use the %EXPORTER_IPV4_ADDRESS in the template) and use zmq with another endpoint, say tcp://*:5557 <tcp://*:5557>

Finally, start your ntopng with an extra interface that collects data from the latter endpoint with -i tcp://127.0.0.1:5557 <tcp://127.0.0.1:5557>

Regards,
Simone



> Example:
> We export flows from 10 different routers (edge01/edge02) in 5 different datacenters. I'd like a interface view for Datacenter1 to include its edge01 and edge02 routers.
>
> Even if I have to know the Probe IP address in advanced and specify it on cmd line, that is fine but the dynamic interfaces are not named what I think the Interface Views feature would expect or reference.
>
> Thanks,
> Ryan
> _______________________________________________
> Ntop mailing list
> Ntop@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop