[f-nsp] XMR sflow source-interface??

Vinny_Abello at Dell.com Vinny_Abello at Dell.com
Tue Aug 16 10:43:02 EDT 2011


Yeah, unfortunately that doesn't exist in Ironware 5.1 on the XMR:

(config)#sflow ?
  destination        Set sflow datagrams export destination
  enable             Enable sflow services
  polling-interval   Set interface counters polling-interval
  sample             Set sample rate

I heard from someone else that this is planned for Ironware 5.3. I also was told that the packets themselves contain an identifier that the collectors can use regardless of the source of the packet. I'm unsure if my collector understands this when collecting from multiple sources on the same destination port (nfdump/nfsen). I'm going to have to check into it... and allow sflow traffic from all interfaces of my XMR's through the firewall where my collector sits. Not ideal, but seems to be all I have to work with until 5.3.

Thanks everyone!

-Vinny

From: Randy McAnally [mailto:rsm at fast-serv.com]
Sent: Monday, August 15, 2011 5:29 PM
To: Abello, Vinny; foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] XMR sflow source-interface??

On Mon, 15 Aug 2011 19:47:52 +0000, Vinny_Abello wrote
> Hi all,
>
> Maybe I'm totally missing something, but is there any way to set the source interface for slow export (like to the loopback) of the XMR platform?

At least on a fastiron:

sflow agent-ip

This option didn't appear until more recent ironware releases though...

~Randy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20110816/86be5260/attachment.html>


More information about the foundry-nsp mailing list