09-10-2018 04:50 AM - edited 03-08-2019 04:07 PM
Have a simple 2 X 93180YC switches configured with Nexus Data Broker (3.5).
Code on the switches is 7.0(3) I7(1).
Problem seeing is traffic coming into the ingress ports from UCS switches ok. However traffic is not being sent to PCAP tool attached on 1/47 of the switch.
I'm focused on the single switch with a single ingress interface (lots of traffic) and egress to the PCAP tool.
I have built a filter with IP range of interest. In connections this is deployed Priority 2. Got 2 x Priority 1 connections which I can't control/delete. Default-Match-IP/Default-Match-ARP/Default-Match-MPLS on these Default-Deny Filters - Is this my problem?? / Is so how do I remove them?
Looking at Stats > Flows for the switch I see plenty of traffic on the ingress port with Action (Output PCAP Interface) - but traffic stats for PCAP Interface is limited to LLDP_Multicast & CDP traffic. Are those default filters stopping and if so how do I overcome this.
I'm not expert here but thing its all in place to work.....
Solved! Go to Solution.
09-13-2018 04:00 AM
TCAM is OK, same config as I have. It looks like your are missing some prerequisites for the nexus 9k described here: Cisco Nexus Data Broker Configuration Guide, Release 3.5 - Prerequisites
Config:
spanning-tree mode mst spanning-tree mst 0-4094 priority 4096 vlan 1-3967 no spanning-tree vlan 1-3967
Can you configure those settings in your environment and test again?
09-10-2018 08:54 AM
Why not use internal Ethanalyzer and store in PCAP file and upload to destination for analyzing.
Make sense ?
09-12-2018 07:33 AM
Are you running NXDB in centralized or embedded mode on those two 9318YC Switches? (having two Prio1. connections makes me think of embedded mode).
On which ports did you attach the UCS? Did you interconnect your NXDB switches? Which ports?
FYI: Priority 1 Connections (Created by Admin) can't be deleted as they are installed on every NXDB switch to prevent traffic flooding when no other forwarding rule is installed. Higher priority rules override those with lower priority so any new connection installed will always overrule the default prio 1 rule.
09-12-2018 08:03 AM
09-12-2018 08:35 AM
09-13-2018 03:42 AM
09-13-2018 04:00 AM
TCAM is OK, same config as I have. It looks like your are missing some prerequisites for the nexus 9k described here: Cisco Nexus Data Broker Configuration Guide, Release 3.5 - Prerequisites
Config:
spanning-tree mode mst spanning-tree mst 0-4094 priority 4096 vlan 1-3967 no spanning-tree vlan 1-3967
Can you configure those settings in your environment and test again?
09-17-2018 07:58 AM
Andreas – Just to loop back here the spanning tree changes seem to have made the difference and the PCAP tool is now getting traffic following the spanning tree changes.
I'm going to replicate the TCAM and Spanning Tree changes on the 2nd switch in the fabric with incoming traffic and then confirm for sure but at the moment traffic into PCAP aligns to the spanning tree changes on Thursday.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide