<?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>topic RE: Info:Kern.IPv4Adj.Info   Table full in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33510#M6375</link>
    <description>Alexandr,&lt;BR /&gt;
&lt;BR /&gt;
As you mentioned, it looks like the table is not full.  As mentioned in the article, this is most likely a temporary hardware / software table sync issue.  If the messages were only seen this one time, I would not worry about it.  If the messages continue to be seen you would want to look into it further to see if the cause may be due to an EXOS code issue.  At that point, if you have a support contract with Extreme, opening a case with GTAC would be advised for further assistance.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Tony</description>
    <pubDate>Wed, 06 Jul 2016 20:01:00 GMT</pubDate>
    <dc:creator>Tony_Thornton</dc:creator>
    <dc:date>2016-07-06T20:01:00Z</dc:date>
    <item>
      <title>Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33506#M6371</link>
      <description>Hello, all!&lt;BR /&gt;
&lt;BR /&gt;
Customer has messages in logs:&lt;BR /&gt;
07/06/2016 11:49:49.69 &lt;I&gt; vrId    2 adj 0x5F430C4F Add Retry failed. (Table full) flags 0&lt;BR /&gt;
07/06/2016 11:49:37.68 &lt;I&gt; vrId    2 adj 0x5F430C13 Add Retry failed. (Table full) flags 200&lt;BR /&gt;
&lt;BR /&gt;
What table is full?&lt;BR /&gt;
In what direction I have to look?&lt;BR /&gt;
&lt;BR /&gt;
Thank you!&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Wed, 06 Jul 2016 14:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33506#M6371</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2016-07-06T14:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33507#M6372</link>
      <description>Hi Alexandr,&lt;BR /&gt;
&lt;BR /&gt;
Below is a link to an article that has a similar message.  Basically, the message indicates the switch was not able to add the entries mentioned in hex into the ARP table as it was full.  Looks like there were two entries that were not added into the hardware table.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/Warn-Kern-IPv4Adj-Warning-log-messages" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/Warn-Kern-IPv4Adj-Warning-log-messages&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
The traffic for those addresses will be forwarded by the CPU (instead of via hardware lookup and ASIC forwarding) so the packets will reach their destination, but there may be some slight increase in latency due to the software (CPU forwarding).&lt;BR /&gt;
&lt;BR /&gt;
Hope this helps.&lt;BR /&gt;
Tony</description>
      <pubDate>Wed, 06 Jul 2016 18:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33507#M6372</guid>
      <dc:creator>Tony_Thornton</dc:creator>
      <dc:date>2016-07-06T18:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33508#M6373</link>
      <description>Hello, Tony!&lt;BR /&gt;
&lt;BR /&gt;
First of all - thank you for quick reply!&lt;BR /&gt;
&lt;BR /&gt;
Output from this switch:&lt;BR /&gt;
# sh iproute reserved-entries statistics&lt;BR /&gt;
                      |-----In HW Route Table-----|   |--In HW L3 Hash Table--|&lt;BR /&gt;
                       # Used Routes   # IPv4 Hosts   IPv4   IPv4  IPv6   IPv4&lt;BR /&gt;
Slot  Type              IPv4   IPv6    Local Remote   Local  Rem.  Local  MCast&lt;BR /&gt;
----  --------------- ------- ------  ------ ------   -----  ----- -----  -----&lt;BR /&gt;
1     X670-48x          14825     40&amp;gt;      -      -     339      0     0   2969&lt;BR /&gt;
&lt;BR /&gt;
Summit X670 can have 6K ARP records in it's table, but we can see that this HW table isn't full. &lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Wed, 06 Jul 2016 19:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33508#M6373</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2016-07-06T19:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33509#M6374</link>
      <description>Also in my case there is Information message.&lt;BR /&gt;
In you example there is Warning message.&lt;BR /&gt;
&lt;BR /&gt;
Thank you!</description>
      <pubDate>Wed, 06 Jul 2016 19:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33509#M6374</guid>
      <dc:creator>Alexandr_P</dc:creator>
      <dc:date>2016-07-06T19:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33510#M6375</link>
      <description>Alexandr,&lt;BR /&gt;
&lt;BR /&gt;
As you mentioned, it looks like the table is not full.  As mentioned in the article, this is most likely a temporary hardware / software table sync issue.  If the messages were only seen this one time, I would not worry about it.  If the messages continue to be seen you would want to look into it further to see if the cause may be due to an EXOS code issue.  At that point, if you have a support contract with Extreme, opening a case with GTAC would be advised for further assistance.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Tony</description>
      <pubDate>Wed, 06 Jul 2016 20:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33510#M6375</guid>
      <dc:creator>Tony_Thornton</dc:creator>
      <dc:date>2016-07-06T20:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: Info:Kern.IPv4Adj.Info   Table full</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33511#M6376</link>
      <description>Alexandr, I agree with what Tony has said.  We have dealt with these messages for at least 3 or 4 years.  Only happens where you have a lot of vlans /vmans and the users are either true Mcast for IPTV or video/ lan leaking UPNP Mcast traffic into core/ lots of routers talking OSPF/ EIGRP/ ect.  We spent a good 3 or 4 months with GTAC to only determine it was indeed the hardware and software tables not being in sync.  As a rule we disable IGMP snooping on all core or aggregation switches so we have assurances Mcast will be forwarded correctly.  Mcast table size has always been a concern and a problem we have had to deal with.  To many people only associate Mcast with IPTV and forget about routing protocols are 100 % dependent  on healthy Mcast in your system.   Good luck</description>
      <pubDate>Wed, 06 Jul 2016 20:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/info-kern-ipv4adj-info-table-full/m-p/33511#M6376</guid>
      <dc:creator>EtherMAN</dc:creator>
      <dc:date>2016-07-06T20:33:00Z</dc:date>
    </item>
  </channel>
</rss>

