Hello,
According to its DataSheet and to its architecture white paper, it seems that the Nexus 3548 does'nt operate in store and forward switching mode. I understand that by default, it forwards in "normal mode" , a sort of cut-through switching mode, and that it can operate in "warp mode" or "warp SPAN mode" for ultra-low latency forwarding.
I Thought that store-and-forward switching mode from 1G ingress link to 10G egress link only applied to other Nexus platforms, like 5000 and 5500.
So why does this bug describe a store-and-forward mode for this platform (Nexus 3548) ?
Second question : if I understand correctly, traffic is corrupted when entering a 1G port and exiting a 10G port, if the 1G link came up after the 10G link. FCS errors increment on the ingress interface. Thus the FCS errors do not come from a physical failure on the ingress link (cable or port or SFP hardware fault) , since flapping the egress link would recover from this issue.
So where do these FCS errors come from ?
Thank you for clarification.
Please find some refering links below :
https://www.cisco.com/c/en/us/products/collateral/switches/nexus-3548-switch/data_sheet_c78-707001.htm
http://docplayer.net/33698293-Cisco-nexus-3548-switch-architecture.html
http://d2zmdbbm9feqrf.cloudfront.net/2012/lat/pdf/BRKARC-1987.pdf
