--- Begin Message ---
I don't know that we can/should draw that conclusion - as you mentioned, you
opened a TAC case but from my understanding it was never driven to a terminal
resolution - either "known limitation, live with it" or "bug, we will/won't fix
it" or "you're doing it wrong". I
--- Begin Message ---
Hi Drew,
Can you specify hardware platform and software version here? I am not seeing
what you're seeing, the config I sent blocks a BGP port scan in nmap, and
prevents BGP peering to anything other than the specified IP. I am testing on
Nexus 9500 with 10.1 NXOS; I
--- Begin Message ---
Hi Drew,
In answer to your question about BGP, the BGP process runs only on the
supervisor engine, it does not run on the linecards or anywhere else. It's a
single process, not a per-interface process or anything like that.
Curious how exactly you are configuring CoPP to
w] size = 256
On Mon, May 13, 2019 at 2:08 PM Tim Stevenson (tstevens) via cisco-nsp
wrote:
>
>
>
>
> -- Forwarded message --
> From: "Tim Stevenson (tstevens)"
> To: Lasse Birnbaum Jensen , "cisco-nsp@puck.nether.net"
>
> Cc:
>
--- Begin Message ---
Should be like this:
tstevens-9236c-1(config)# line vty
tstevens-9236c-1(config-line)# ip
ip ipv6
tstevens-9236c-1(config-line)# ip access-class foo in
tstevens-9236c-1(config-line)# ipv6 access-class bar in
tstevens-9236c-1(config-line)# sh run | sec vty
line vty
--- Begin Message ---
First gen n9k does not support Netflow at all, only sflow. 2nd gen (EX/FX/FX2)
support both, but there is the SPAN+SFlow limitation (we are working on fixing
that for FX2, which can theoretically support these concurrently).
For recommended sampling value, we set the rate
--- Begin Message ---
Release notes have this information. EX & FX are both supported. 3600-R is not.
See Table 2/Table 3 here:
https://www.cisco.com/c/en/us/td/docs/net_mgmt/xnc/nexus_data_broker/release_notes/Nexus_Data_Broker_Release_Notes_371.html
Hope that helps,
Tim
-Original
--- Begin Message ---
Please check the config guide. I am not as familiar w/the 1st gen switches as
2nd gen, but there should be at least some level of reconfigurability of the
regions in gen 1. So you may be able to size up the region you want by removing
entries from some other region.
Yes,
--- Begin Message ---
Yes, ACL lines consume space in the TCAM. TCAM can be recarved according to the
features in use/required.
As long as the policy fits in the available TCAM space for that feature
(software will complain and fail your config if it won't), enforcement is at
full rate, no
--- Begin Message ---
-Original Message-
From: Satish Patel
Sent: Wednesday, March 20, 2019 10:23 AM
To: Tim Stevenson (tstevens)
Cc: Nick Cutting ; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Nexus 9300 sflow performance
Thanks Tim,
Here is the output of show hardware
--- Begin Message ---
Yes, this is 1st gen. The SFLOW/SPAN restriction should not apply there.
Re: 60Gbps/24Mpps and SFLOW, SFLOW does not do aggregation of stats for flows
in the switch like netflow does - it's just 1-in-n packet sampling. As such,
the value of "n" should be high enough that
--- Begin Message ---
Make sure you distinguish between N9300 (1st generation) and N9300-EX/FX/FX2
(2nd generation). The SFLOW + SPAN limitation applies only to the latter. It's
also on the latter that Netflow is supported, which can run concurrently with
SPAN sessions.
Tim
-Original
--- Begin Message ---
Hi Brad,
I checked this on n7700 F3 - concur that even w/'statistics per-entry', the hit
count is not incrementing in 'sh ip access' output when the ACL is used for QOS
classification. Same behavior in 8.3.1.
>From what I see, the statistics are in fact incrementing in
--- Begin Message ---
There isn't one. Closest is Nexus 3636C-R, this is J+ based like the 9636C-RX
but with on-chip tables only (no external TCAM).
Tim
-Original Message-
From: cisco-nsp On Behalf Of Drew Weaver
Sent: Wednesday, August 8, 2018 5:39 AM
To: cisco-nsp@puck.nether.net
16
Eth1/351a004400 10102 255 136 -13 1224
Eth1/361a004600 10106 255 140 -13 1632
BR,
Pedro Caetano
On Mon, Jun 25, 2018 at 2:00 PM, Tim Stevenson (tstevens) via cisco-nsp <
cisco-nsp@puck.nether.net>
--- Begin Message ---
Not aware of a single document that will show that for all platforms. Best way
is "show interface hardware-mappings". "Unit" and "Slice" are the main points
of reference (unit == ASIC instance, slice == pipeline).
E.g., 93180yc-ex:
leaf1# sh int hard
Legends:
SMod
16 matches
Mail list logo
