Bottom line is we need to configure span-sflow <size>  now its
working... Thanks for your help Nick!

# show run all | grep "tcam region s"
hardware access-list tcam region span 0
hardware access-list tcam region svi 0
hardware access-list tcam region sflow 0
hardware access-list tcam region span 0
hardware access-list tcam region span-sflow 256

No error anymore now...

(config)# sflow data-source interface e2/5
(config)#

On Fri, Apr 5, 2019 at 4:34 PM Satish Patel <[email protected]> wrote:
>
> Nick,
>
> Bummer!!!  it didn't work, why its saying span-sflow
>
> # show run all | grep "tcam region s"
> hardware access-list tcam region span 0
> hardware access-list tcam region svi 0
> hardware access-list tcam region span 0
> hardware access-list tcam region span-sflow 0
> hardware access-list tcam region sflow 256
>
>
> (config)# sflow data-source interface e2/5
> In order to enable sFlow sampling on North star front panel
> port(Ethernet2/5), please either carve both span and sflow tcam
> regions with non-zero sizes using the commands
> 'hardware access-list tcam region span <size>'
> 'hardware access-list tcam region sflow <size>'
> or remove both span and sflow tcam regions and carve a span-sflow tcam
> region with a non-zero size using the commands
> swt-dist1-010101-hd-1-5(config)#
>
> On Fri, Apr 5, 2019 at 4:23 PM Satish Patel <[email protected]> wrote:
> >
> > Nick,
> >
> > One thing is very interesting if i configure "sflow data-source int
> > e1/1" it letting me do that no error but only throwing error if i try
> > on 40G interface
> >
> > On Fri, Apr 5, 2019 at 4:09 PM Satish Patel <[email protected]> wrote:
> > >
> > > Got it what you trying to say.....  let me try and see if it works
> > >
> > > On Fri, Apr 5, 2019 at 4:04 PM Nick Cutting <[email protected]> wrote:
> > > >
> > > > I don’t know if that would work.
> > > >
> > > > There is a specific relationship between the SPAN and the SFLOW.  I 
> > > > think it uses the same part of the TCAM.
> > > >
> > > >
> > > >
> > > > From: Satish Patel <[email protected]>
> > > > Sent: Friday, April 5, 2019 4:03 PM
> > > > To: Nick Cutting <[email protected]>
> > > > Subject: Re: [c-nsp] Cisco Nexus 9K tcam carving question
> > > >
> > > >
> > > >
> > > > This message originated from outside your organization.
> > > >
> > > > We are not using ipv6 so why don't i give "hardware access-list tcam
> > > > region rp-ipv6-qos 256" slice to sflow?
> > > >
> > > > On Fri, Apr 5, 2019 at 4:02 PM Nick Cutting <[email protected]> wrote:
> > > > >
> > > > > yes exactly right - I cannot test it on my Gen1 9300, as we are using 
> > > > > span, but it was very similar when I did it to the 9300-EX
> > > > >
> > > > >
> > > > >
> > > > > From: Satish Patel <[email protected]>
> > > > > Sent: Friday, April 5, 2019 4:00 PM
> > > > > To: Nick Cutting <[email protected]>
> > > > > Subject: Re: [c-nsp] Cisco Nexus 9K tcam carving question
> > > > >
> > > > >
> > > > >
> > > > > This message originated from outside your organization.
> > > > >
> > > > > You are saying make span to 0 and give it slice to sflow right?
> > > > > something like following command?
> > > > >
> > > > > hardware access-list tcam region span 0
> > > > >
> > > > > hardware access-list tcam region sflow 256
> > > > >
> > > > > On Fri, Apr 5, 2019 at 3:56 PM Satish Patel <[email protected]> 
> > > > > wrote:
> > > > > >
> > > > > > No i don't think we need SPAN port or any kind of traffic mirroring,
> > > > > > all i care about sflow.
> > > > > >
> > > > > > Here is the output of my switch
> > > > > >
> > > > > > (config)# sh run all | in "tcam region s"
> > > > > > hardware access-list tcam region span 256
> > > > > > hardware access-list tcam region svi 0
> > > > > > hardware access-list tcam region sflow 0
> > > > > > hardware access-list tcam region span 0
> > > > > > hardware access-list tcam region span-sflow 0
> > > > > >
> > > > > > On Fri, Apr 5, 2019 at 3:35 PM Nick Cutting <[email protected]> 
> > > > > > wrote:
> > > > > > >
> > > > > > > If you don't need SPAN
> > > > > > >
> > > > > > > Type this first, before adding the sflow carve
> > > > > > >
> > > > > > > hardware access-list tcam region span 0
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: cisco-nsp <[email protected]> On Behalf Of 
> > > > > > > Satish Patel
> > > > > > > Sent: Friday, April 5, 2019 3:15 PM
> > > > > > > To: Cisco Network Service Providers <[email protected]>
> > > > > > > Subject: [c-nsp] Cisco Nexus 9K tcam carving question
> > > > > > >
> > > > > > > This message originates from outside of your organisation.
> > > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > I want to enable sFlow on Cisco nexus 9300 switch on 40G interface
> > > > > > > (GEM) module. but getting following error.
> > > > > > >
> > > > > > > (config)# sflow data-source interface e2/5 In order to enable 
> > > > > > > sFlow sampling on North star front panel port(Ethernet2/5), 
> > > > > > > please either carve both span and sflow tcam regions with 
> > > > > > > non-zero sizes using the commands 'hardware access-list tcam 
> > > > > > > region span <size>'
> > > > > > > 'hardware access-list tcam region sflow <size>'
> > > > > > > or remove both span and sflow tcam regions and carve a span-sflow 
> > > > > > > tcam region with a non-zero size using the commands
> > > > > > >
> > > > > > >
> > > > > > > When i am doing following, got error that means i don't have 
> > > > > > > space in my tcam table so what is the best approve here?
> > > > > > >
> > > > > > > (config)# hardware access-list tcam region sflow 256
> > > > > > > ERROR: Aggregate TCAM region configuration exceeded the available 
> > > > > > > Ingress TCAM slices. Please re-configure.
> > > > > > > _______________________________________________
> > > > > > > cisco-nsp mailing list [email protected] 
> > > > > > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > > > >
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to