<?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 SNMP LLDP neighborhood (lldpRem) in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/snmp-lldp-neighborhood-lldprem/m-p/8330#M3</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
First post for me on this hub. I report here a problem that I detected using an open-based tools called netdisco retrieving lldp neighborhood informations.&lt;BR /&gt;
&lt;BR /&gt;
Where getting trouble polling our ERS4950 Mib's OID iso.0.8802.1.1.2.1.4 (lldpRemoteSystemsData) because output format change for sub-oids iso.0.8802.1.1.2.1.4.1 and iso.0.8802.1.1.2.1.4.2 which respectively are (extracts, example in bold):&lt;BR /&gt;
&lt;BR /&gt;
- iso.0.8802.1.1.2.1.4.1 (lldpRemTable)&lt;BR /&gt;
  &lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.554168.48.3 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.10024103.50.31 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.10163161.434.32 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15315603.414.20 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319201.406.12 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319326.410.15 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319402.399.6 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15320301.412.17 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15320828.402.8 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15321318.413.19 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15321910.405.11 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15322078.409.14 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15322305.407.13 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15323611.417.23 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15323806.408.18 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15324017.403.9 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15324601.404.10 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325211.398.5 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325895.411.16 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325896.400.7 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15326100.416.22 = INTEGER: 4&lt;BR /&gt;
&lt;I&gt;&lt;U&gt;iso.0.8802.1.1.2.1.4.1.1.4.&lt;/U&gt;&lt;/I&gt;&lt;B&gt;&lt;I&gt;&lt;U&gt;15327800&lt;/U&gt;&lt;/I&gt;&lt;/B&gt;&lt;I&gt;&lt;U&gt;.397.4 = INTEGER: 4&lt;/U&gt;&lt;/I&gt;&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15328099.415.21 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82307038.8.46 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82309831.10.49 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82309836.7.48 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82310121.6.47 = INTEGER: 4&lt;BR /&gt;
&lt;BR /&gt;
- iso.0.8802.1.1.2.1.4.2 (lldpRemManAddrTable):&lt;BR /&gt;
    &lt;BR /&gt;
&lt;I&gt;&lt;U&gt;iso.0.8802.1.1.2.1.4.2.1.3.&lt;/U&gt;&lt;/I&gt;&lt;B&gt;&lt;I&gt;&lt;U&gt;0&lt;/U&gt;&lt;/I&gt;&lt;/B&gt;&lt;I&gt;&lt;U&gt;.397.4.1.4.192.168.200.242 = INTEGER: 2&lt;/U&gt;&lt;/I&gt;&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.398.5.1.4.192.168.200.48 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.399.6.1.4.192.168.200.56 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.400.7.1.4.192.168.201.54 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.402.8.1.4.192.168.201.56 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.403.9.1.4.192.168.201.59 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.404.10.1.4.192.168.201.29 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.405.11.1.4.192.168.201.55 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.406.12.1.4.192.168.201.57 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.407.13.1.4.192.168.201.30 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.408.18.1.4.192.168.200.28 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.409.14.1.4.192.168.200.21 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.410.15.1.4.192.168.200.22 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.411.16.1.4.192.168.200.45 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.412.17.1.4.192.168.200.47 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.413.19.1.4.192.168.200.27 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.414.20.1.4.192.168.200.29 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.415.21.1.4.192.168.201.26 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.416.22.1.4.192.168.200.24 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.417.23.1.4.192.168.201.58 = INTEGER: 2&lt;BR /&gt;
    &lt;BR /&gt;
&lt;BR /&gt;
The second one retrieve neighbor's IP address, but the format:&lt;BR /&gt;
&lt;BR /&gt;
 "iso.0.8802.1.1.2.1.4.2.1.3.&lt;B&gt;0&lt;/B&gt;.&amp;lt;&lt;B&gt;ifNumber&lt;/B&gt;&amp;gt;.1.4.&amp;lt;&lt;B&gt;neighbor_IP_address&lt;/B&gt;&amp;gt;"&lt;BR /&gt;
&lt;BR /&gt;
doesn't match the first one format (0 is replaced by a number which I dont' know the signification).&lt;BR /&gt;
&lt;BR /&gt;
This behaviour, which is not observable on our old Avaya's ERS4550 (which don't insert a zero on lldpRemManAddrTable) disrupt our collecting software, which is unable to retrieve neighbor information correctly.&lt;BR /&gt;
&lt;BR /&gt;
Do you think it's a normal behaviour and we have to fix the problem on the software or that it's a Extreme OS bug ?&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your help.&lt;BR /&gt;
&lt;BR /&gt;
Model: ERS4950GTS-PWR&lt;BR /&gt;
Software version: 7.5.0.007&lt;BR /&gt;</description>
    <pubDate>Mon, 30 Apr 2018 14:14:00 GMT</pubDate>
    <dc:creator>Rodjeur69</dc:creator>
    <dc:date>2018-04-30T14:14:00Z</dc:date>
    <item>
      <title>SNMP LLDP neighborhood (lldpRem)</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/snmp-lldp-neighborhood-lldprem/m-p/8330#M3</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
First post for me on this hub. I report here a problem that I detected using an open-based tools called netdisco retrieving lldp neighborhood informations.&lt;BR /&gt;
&lt;BR /&gt;
Where getting trouble polling our ERS4950 Mib's OID iso.0.8802.1.1.2.1.4 (lldpRemoteSystemsData) because output format change for sub-oids iso.0.8802.1.1.2.1.4.1 and iso.0.8802.1.1.2.1.4.2 which respectively are (extracts, example in bold):&lt;BR /&gt;
&lt;BR /&gt;
- iso.0.8802.1.1.2.1.4.1 (lldpRemTable)&lt;BR /&gt;
  &lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.554168.48.3 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.10024103.50.31 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.10163161.434.32 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15315603.414.20 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319201.406.12 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319326.410.15 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15319402.399.6 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15320301.412.17 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15320828.402.8 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15321318.413.19 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15321910.405.11 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15322078.409.14 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15322305.407.13 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15323611.417.23 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15323806.408.18 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15324017.403.9 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15324601.404.10 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325211.398.5 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325895.411.16 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15325896.400.7 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15326100.416.22 = INTEGER: 4&lt;BR /&gt;
&lt;I&gt;&lt;U&gt;iso.0.8802.1.1.2.1.4.1.1.4.&lt;/U&gt;&lt;/I&gt;&lt;B&gt;&lt;I&gt;&lt;U&gt;15327800&lt;/U&gt;&lt;/I&gt;&lt;/B&gt;&lt;I&gt;&lt;U&gt;.397.4 = INTEGER: 4&lt;/U&gt;&lt;/I&gt;&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.15328099.415.21 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82307038.8.46 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82309831.10.49 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82309836.7.48 = INTEGER: 4&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.1.1.4.82310121.6.47 = INTEGER: 4&lt;BR /&gt;
&lt;BR /&gt;
- iso.0.8802.1.1.2.1.4.2 (lldpRemManAddrTable):&lt;BR /&gt;
    &lt;BR /&gt;
&lt;I&gt;&lt;U&gt;iso.0.8802.1.1.2.1.4.2.1.3.&lt;/U&gt;&lt;/I&gt;&lt;B&gt;&lt;I&gt;&lt;U&gt;0&lt;/U&gt;&lt;/I&gt;&lt;/B&gt;&lt;I&gt;&lt;U&gt;.397.4.1.4.192.168.200.242 = INTEGER: 2&lt;/U&gt;&lt;/I&gt;&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.398.5.1.4.192.168.200.48 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.399.6.1.4.192.168.200.56 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.400.7.1.4.192.168.201.54 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.402.8.1.4.192.168.201.56 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.403.9.1.4.192.168.201.59 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.404.10.1.4.192.168.201.29 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.405.11.1.4.192.168.201.55 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.406.12.1.4.192.168.201.57 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.407.13.1.4.192.168.201.30 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.408.18.1.4.192.168.200.28 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.409.14.1.4.192.168.200.21 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.410.15.1.4.192.168.200.22 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.411.16.1.4.192.168.200.45 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.412.17.1.4.192.168.200.47 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.413.19.1.4.192.168.200.27 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.414.20.1.4.192.168.200.29 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.415.21.1.4.192.168.201.26 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.416.22.1.4.192.168.200.24 = INTEGER: 2&lt;BR /&gt;
iso.0.8802.1.1.2.1.4.2.1.3.0.417.23.1.4.192.168.201.58 = INTEGER: 2&lt;BR /&gt;
    &lt;BR /&gt;
&lt;BR /&gt;
The second one retrieve neighbor's IP address, but the format:&lt;BR /&gt;
&lt;BR /&gt;
 "iso.0.8802.1.1.2.1.4.2.1.3.&lt;B&gt;0&lt;/B&gt;.&amp;lt;&lt;B&gt;ifNumber&lt;/B&gt;&amp;gt;.1.4.&amp;lt;&lt;B&gt;neighbor_IP_address&lt;/B&gt;&amp;gt;"&lt;BR /&gt;
&lt;BR /&gt;
doesn't match the first one format (0 is replaced by a number which I dont' know the signification).&lt;BR /&gt;
&lt;BR /&gt;
This behaviour, which is not observable on our old Avaya's ERS4550 (which don't insert a zero on lldpRemManAddrTable) disrupt our collecting software, which is unable to retrieve neighbor information correctly.&lt;BR /&gt;
&lt;BR /&gt;
Do you think it's a normal behaviour and we have to fix the problem on the software or that it's a Extreme OS bug ?&lt;BR /&gt;
&lt;BR /&gt;
Thanks for your help.&lt;BR /&gt;
&lt;BR /&gt;
Model: ERS4950GTS-PWR&lt;BR /&gt;
Software version: 7.5.0.007&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Apr 2018 14:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/snmp-lldp-neighborhood-lldprem/m-p/8330#M3</guid>
      <dc:creator>Rodjeur69</dc:creator>
      <dc:date>2018-04-30T14:14:00Z</dc:date>
    </item>
  </channel>
</rss>

