cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
398
Views
5
Helpful
1
Replies
Peyman Zadmehr
Beginner

Nexus 9336C-FX2 Maximum MAC address table size...

Hi In following link it was mentioned the Maximum supported MAC address is 256K for Nexus 9336C-FX2: https://www.cisco.com/c/en/us/products/collateral/switches/nexus-9000-series-switches/datasheet-c78-742282.html

But in Following link it is 92K

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/93x/scalability/guide-933/b-Cisco_Nexus-9000-Series-NX-OS-Verified-Scalability-Guide-933.html

This is really confusing. Which one is correct? And What will happen if we pass this limit? Will the traffic blocked or Broadcasted(Same as Catalyst Switches)

1 ACCEPTED SOLUTION

Accepted Solutions
kkhlebop
Cisco Employee

Verified scalability guide, provides a verified number that is supported by both software and hardware, where the data sheet states what are values supported by hardware only (as table 3 headline states in the data sheet). If the user exceeds the verified limit, new entries will not be part of the table and traffic will be forwarded as an unknown unicast. More on this below:

 

When the packet/frame comes to the switch, this packet will come with unique a SMAC or DMAC, switch will not find DMAC in table (as table is full and not new entries are learned), that way switch will replicate this packet without changing mac addresses and send it to everybody, in this case this is not broadcast packet (explained about why is not) but unknown unicast (even does behave as broadcast in a sense it is flooded to everybody).

View solution in original post

1 REPLY 1
kkhlebop
Cisco Employee

Verified scalability guide, provides a verified number that is supported by both software and hardware, where the data sheet states what are values supported by hardware only (as table 3 headline states in the data sheet). If the user exceeds the verified limit, new entries will not be part of the table and traffic will be forwarded as an unknown unicast. More on this below:

 

When the packet/frame comes to the switch, this packet will come with unique a SMAC or DMAC, switch will not find DMAC in table (as table is full and not new entries are learned), that way switch will replicate this packet without changing mac addresses and send it to everybody, in this case this is not broadcast packet (explained about why is not) but unknown unicast (even does behave as broadcast in a sense it is flooded to everybody).

View solution in original post

Content for Community-Ad

This widget could not be displayed.