[c-nsp] Cisco Nexus 9K tcam carving question

[Satish Patel]

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 <satish.txt at gmail.com> 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 <ncutting at edgetg.com> 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 <satish.txt at gmail.com>
> > Sent: Friday, April 5, 2019 4:03 PM
> > To: Nick Cutting <ncutting at edgetg.com>
> > 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 <ncutting at edgetg.com> 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 <satish.txt at gmail.com>
> > > Sent: Friday, April 5, 2019 4:00 PM
> > > To: Nick Cutting <ncutting at edgetg.com>
> > > 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 <satish.txt at gmail.com> 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 <ncutting at edgetg.com> 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 <cisco-nsp-bounces at puck.nether.net> On Behalf Of Satish Patel
> > > > > Sent: Friday, April 5, 2019 3:15 PM
> > > > > To: Cisco Network Service Providers <cisco-nsp at puck.nether.net>
> > > > > 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 cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > >