<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>T-SeriesのトピックRe: T1040 L2 switch frame fragmentation problem</title>
    <link>https://community.nxp.com/t5/T-Series/T1040-L2-switch-frame-fragmentation-problem/m-p/693607#M2151</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;SPAN style="font-size: 12.0pt;"&gt;Szymon Kukliński&lt;/SPAN&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please try whether increasing the value VTSS_MAX_FRAME_LENGTH_MAX according to your requirement would be helpful. In the default config, it is defined as "10240" in include/vtss_api/vtss_port_api.h of l2switch source code.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jun 2017 09:53:37 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2017-06-02T09:53:37Z</dc:date>
    <item>
      <title>T1040 L2 switch frame fragmentation problem</title>
      <link>https://community.nxp.com/t5/T-Series/T1040-L2-switch-frame-fragmentation-problem/m-p/693606#M2150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During our tests we found out that the integrated Ethernet switch internal port has problems with handling a specific traffic type. We established that the switch drops frames arriving at chip_port 9 and marks them as fragments (rmon.rx_etherStatsFragments in vtss_port_counters_t struct according to Microsemi API). Interestingly this problem does not occur on other ports (we tested the exact same traffic type between on chip_ports 0 and 1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is very easy to recreate this problem (as seen between chip_ports 0 and 8):&lt;/P&gt;&lt;P&gt;# ping6 2001::2 -c1 -s20000&lt;/P&gt;&lt;P&gt;PING 2001::2(2001::2) 20000 data bytes&lt;/P&gt;&lt;P&gt;--- 2001::2 ping statistics ---&lt;/P&gt;&lt;P&gt;1 packets transmitted, 0 received, 100% packet loss, time 0ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;expected behaviour (as seen between chip_ports 0 and 1):&lt;/P&gt;&lt;P&gt;# ping6 2001::2 -c1 -s20000&lt;/P&gt;&lt;P&gt;PING 2001::2(2001::2) 20000 data bytes&lt;/P&gt;&lt;P&gt;20008 bytes from 2001::2: icmp_seq=1 ttl=64 time=0.932 ms&lt;/P&gt;&lt;P&gt;--- 2001::2 ping statistics ---&lt;/P&gt;&lt;P&gt;1 packets transmitted, 1 received, 0% packet loss, time 0ms&lt;/P&gt;&lt;P&gt;rtt min/avg/max/mdev = 0.932/0.932/0.932/0.000 ms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I measured that the maximum data bytes size is&amp;nbsp;15920 for ping6 and&amp;nbsp;16272 for ping. Every ping larger than that gets dropped and caused &lt;SPAN&gt;rmon.rx_etherStatsFragments to increment.&lt;/SPAN&gt;&amp;nbsp;The intrrface from which the frame originates is configured as 802.1ad:&lt;/P&gt;&lt;P&gt;ip -d link show mgmt&lt;BR /&gt;9: mgmt@eth1: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc noqueue state UP mode DEFAULT group default&lt;BR /&gt; link/ether 00:80:ea:0f:24:90 brd ff:ff:ff:ff:ff:ff promiscuity 0&lt;BR /&gt; vlan protocol 802.1ad id 100 &amp;lt;REORDER_HDR&amp;gt; numtxqueues 1 numrxqueues 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The internal switch is configured by our own driver based on NXP l2switch program and our previous experience with Vitesse/Microsemi switches. The most crucial port settings are:&lt;/P&gt;&lt;P&gt;1. vtss_port_map_t&amp;nbsp;&lt;BR /&gt;{&lt;BR /&gt; /* chip_port, chip_no, miim_controller, miim_addr, miim_chip_no */&lt;BR /&gt; {0, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0}, //lower slot&lt;BR /&gt; {1, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0}, //upper slot&lt;BR /&gt; {2, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0},&lt;BR /&gt; {3, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0},&lt;BR /&gt; {8, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0}, //CPU&lt;BR /&gt; {9, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0}, //CPU&lt;BR /&gt; {CHIP_PORT_UNUSED, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0},&lt;BR /&gt; {CHIP_PORT_UNUSED, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0},&lt;BR /&gt; {CHIP_PORT_UNUSED, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0},&lt;BR /&gt; {CHIP_PORT_UNUSED, 0, VTSS_MIIM_CONTROLLER_NONE, 0, 0}&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. vtss_port_conf_t:&lt;/P&gt;&lt;P&gt;/* if_type, sd_enable, sd_active_high, sd_internal, frame_gaps, power_down, speed,&lt;BR /&gt; * fdx, flow_control, max_frame_length&lt;BR /&gt; * max_tags, exc_col_cont, xaui_rx_lane_flip, xaui_tx_lane_flip, loop, serdes */&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;chip_port 0:&lt;/STRONG&gt;&lt;BR /&gt; {VTSS_PORT_INTERFACE_SGMII, 0, 0, 0, {0, 0, 0}, 0, VTSS_SPEED_1G,&lt;BR /&gt; 1, {1, 1, {0}, {0}}, VTSS_MAX_FRAME_LENGTH_MAX,&lt;BR /&gt; VTSS_PORT_MAX_TAGS_TWO, 0, 0, 0, VTSS_PORT_LOOP_DISABLE, {1}},&lt;/P&gt;&lt;P&gt;(&lt;STRONG&gt;chip_port 1,&amp;nbsp;chip_port 2 and&amp;nbsp;chip_port 3 are configured as&amp;nbsp;chip_port 0&lt;/STRONG&gt;)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;chip_port 8:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;{VTSS_PORT_INTERFACE_VAUI, 0, 0, 0, {0, 0, 0}, 0, VTSS_SPEED_2500M,&lt;BR /&gt; 1, {1, 1, {0}, {0}}, VTSS_MAX_FRAME_LENGTH_MAX,&lt;BR /&gt; VTSS_PORT_MAX_TAGS_TWO, 0, 0, 0, VTSS_PORT_LOOP_DISABLE, {1}},&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;chip_port 9:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;{VTSS_PORT_INTERFACE_VAUI, 0, 0, 0, {0, 0, 0}, 0, VTSS_SPEED_2500M,&lt;BR /&gt; 1, {1, 1, {0}, {0}}, VTSS_MAX_FRAME_LENGTH_MAX,&lt;BR /&gt; VTSS_PORT_MAX_TAGS_TWO, 0, 0, 0, VTSS_PORT_LOOP_DISABLE, {1}},&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12.0pt;"&gt;Szymon Kukliński&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 May 2017 13:37:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1040-L2-switch-frame-fragmentation-problem/m-p/693606#M2150</guid>
      <dc:creator>elszymono</dc:creator>
      <dc:date>2017-05-25T13:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: T1040 L2 switch frame fragmentation problem</title>
      <link>https://community.nxp.com/t5/T-Series/T1040-L2-switch-frame-fragmentation-problem/m-p/693607#M2151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;SPAN style="font-size: 12.0pt;"&gt;Szymon Kukliński&lt;/SPAN&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please try whether increasing the value VTSS_MAX_FRAME_LENGTH_MAX according to your requirement would be helpful. In the default config, it is defined as "10240" in include/vtss_api/vtss_port_api.h of l2switch source code.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jun 2017 09:53:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/T1040-L2-switch-frame-fragmentation-problem/m-p/693607#M2151</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2017-06-02T09:53:37Z</dc:date>
    </item>
  </channel>
</rss>

