<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[AlliedTelesis - network topology]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I want to understand how "Show VLAN" takes the VLAN information from the switch? I have AT-GS950/24 and AT-GS950/48 port L2 and L3 switches however only /24 can display VLAN information. I have compiled AT private MIB and then when I do snmpwalk on it - it displays the VLAN information. Is there an option to MAP this information to display proper VLAN information in "Show VLANs" section?</p>
<p dir="auto">My second question is that in Object details, PORTS section doesn't display the port configuration but blank screen. I saw that on interface section the "Port" column is empty. Again my question is: Is it possible to map the data taken from the private MIB to this section?</p>
<p dir="auto">I have attached screenshots from the console.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000001182-Screen_Shot_2013-05-30_at_10.04.40.png" alt="Screen Shot 2013-05-30 at 10.04.40.png" class="img-markdown  img-fluid" width="1375" height="803" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000001184-Screen_Shot_2013-05-30_at_10.07.12.png" alt="Screen Shot 2013-05-30 at 10.07.12.png" class="img-markdown  img-fluid" width="1794" height="1096" /></p>
]]></description><link>https://forum.netxms.org/topic/2407/alliedtelesis-network-topology</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 10:06:17 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/2407.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 30 May 2013 07:07:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to AlliedTelesis - network topology on Sun, 09 Sep 2018 15:55:59 GMT]]></title><description><![CDATA[<p dir="auto">I have a similar issue with some dlink switches (not with netgear and cisco switches).</p>
<p dir="auto">I get "VLAN list successfully retrieved from node"</p>
<p dir="auto">[09.09.2018 20:54:13] **** Poll request sent to server ****<br />
[09.09.2018 20:54:14] Poll request accepted<br />
[09.09.2018 20:54:14] Starting topology poll for node Library<br />
[09.09.2018 20:54:14] VLAN list successfully retrieved from node<br />
[09.09.2018 20:54:20] Switch forwarding database retrieved<br />
[09.09.2018 20:54:21] Link layer topology retrieved (1 connections found)<br />
[09.09.2018 20:54:21] Updating peer information on interfaces<br />
[09.09.2018 20:54:21] Link layer topology processed<br />
[09.09.2018 20:54:21] Finished topology poll for node Library<br />
[09.09.2018 20:54:21] **** Poll completed successfully ****</p>
<p dir="auto">but nothing shows up in the dlink VLAN column on the interfaces tab (cisco and netgear switch interface tabs show vlan information in vlan column)</p>
<p dir="auto">Dlink MIB seems to be loaded because in the netxms MIB browser for the dlink switch I can see the vlan table OID for the switch, with OID as text and description filled as below, and SNMP walking it gives me vlan names and egress and untagged members</p>
<p dir="auto">.1.3.6.1.4.1.171.10.76.9.7.6.1</p>
<p dir="auto">.iso.org.dod.internet.private.enterprises.d-link.dlink-products.dlink-DGS1210SeriesProd.dgs-1210-16ax.companyDot1qVlanGroup.dot1qVlanTable.dot1qVlanEntry</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000004194-netxms-novlan.JPG" alt="netxms-novlan.JPG" class="img-markdown  img-fluid" width="1396" height="348" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000004196-netxms-novlan2.JPG" alt="netxms-novlan2.JPG" class="img-markdown  img-fluid" width="133" height="364" /></p>
]]></description><link>https://forum.netxms.org/post/24792</link><guid isPermaLink="true">https://forum.netxms.org/post/24792</guid><dc:creator><![CDATA[sarangtc]]></dc:creator><pubDate>Sun, 09 Sep 2018 15:55:59 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Tue, 11 Feb 2014 12:37:57 GMT]]></title><description><![CDATA[<p dir="auto">You've got a message.  <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forum.netxms.org/post/12754</link><guid isPermaLink="true">https://forum.netxms.org/post/12754</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Tue, 11 Feb 2014 12:37:57 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Mon, 10 Feb 2014 23:49:16 GMT]]></title><description><![CDATA[<p dir="auto">Access to real equipment can really help. Can you contact me directly so we can organize it?</p>
]]></description><link>https://forum.netxms.org/post/12746</link><guid isPermaLink="true">https://forum.netxms.org/post/12746</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 10 Feb 2014 23:49:16 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Tue, 04 Feb 2014 09:01:46 GMT]]></title><description><![CDATA[<p dir="auto">First of all, thank you for unlocking the topic.</p>
<p dir="auto">The AT NDD driver seem to work only partially.<br />
For GS950/48 I was able to see the switch port presentation (see on the attachment) however VLAN table is not shown correctly (it's empty). The correct OID that will collect VLAN information is <strong>.1.3.6.1.4.1.207.8.33.8</strong>. It will show this data:</p>
<p dir="auto"># snmpwalk -c ******** -v 2c 10.7.0.6 .1.3.6.1.4.1.207.8.33.8<br />
iso.3.6.1.4.1.207.8.33.8.1.1.1.1 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.1.1.1.102 = INTEGER: 102<br />
iso.3.6.1.4.1.207.8.33.8.1.1.1.400 = INTEGER: 400<br />
iso.3.6.1.4.1.207.8.33.8.1.1.2.1 = STRING: "Default VLAN"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.2.102 = STRING: "WiFi"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.2.400 = STRING: "Newell"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.3.1 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.1.1.3.102 = INTEGER: 102<br />
iso.3.6.1.4.1.207.8.33.8.1.1.3.400 = INTEGER: 400<br />
iso.3.6.1.4.1.207.8.33.8.1.1.4.1 = STRING: "1-2,4,6-16,22,25-48"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.4.102 = ""<br />
iso.3.6.1.4.1.207.8.33.8.1.1.4.400 = STRING: "3,5,17-21,23-24"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.5.1 = ""<br />
iso.3.6.1.4.1.207.8.33.8.1.1.5.102 = STRING: "16,47"<br />
iso.3.6.1.4.1.207.8.33.8.1.1.5.400 = ""<br />
iso.3.6.1.4.1.207.8.33.8.1.1.20.1 = INTEGER: 2<br />
iso.3.6.1.4.1.207.8.33.8.1.1.20.102 = INTEGER: 2<br />
iso.3.6.1.4.1.207.8.33.8.1.1.20.400 = INTEGER: 2<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.1 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.2 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.3 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.4 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.5 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.6 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.7 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.8 = INTEGER: 1<br />
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.9 = INTEGER: 1<br />
...<br />
...</p>
<p dir="auto">With GS950/24 the problem is quite the opposite. There is now switch port information shown (PORT tab), however VLAN database is shown correctly (without port-to-vlan presentation).<br />
If needed I can provide access to my NetXMS installation so you can perform any kind of tests you like. Just let me know.</p>
<p dir="auto">Regards,<br />
Iliyan</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000001582-Screen_Shot_2014-02-04_at_10.55.17.png" alt="Screen Shot 2014-02-04 at 10.55.17.png" class="img-markdown  img-fluid" width="3588" height="2190" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000001584-Screen_Shot_2014-02-04_at_11.00.09.png" alt="Screen Shot 2014-02-04 at 11.00.09.png" class="img-markdown  img-fluid" width="3588" height="2190" /></p>
]]></description><link>https://forum.netxms.org/post/12664</link><guid isPermaLink="true">https://forum.netxms.org/post/12664</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Tue, 04 Feb 2014 09:01:46 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Fri, 04 Oct 2013 08:42:45 GMT]]></title><description><![CDATA[<p dir="auto">Thanks. Btw, have you consider adding Mikrotik NDD as well?</p>
]]></description><link>https://forum.netxms.org/post/11456</link><guid isPermaLink="true">https://forum.netxms.org/post/11456</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Fri, 04 Oct 2013 08:42:45 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Thu, 03 Oct 2013 21:09:27 GMT]]></title><description><![CDATA[<p dir="auto">Sorry, not yet. At some point I completely forgot about it <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--disappointed" style="height:1.4em;width:auto;vertical-align:middle" title=":(" alt="😞" /> I've added a bugtracker issue (<a href="https://www.radensolutions.com/chiliproject/issues/367" rel="nofollow ugc">https://www.radensolutions.com/chiliproject/issues/367</a>) so it will not be forgotten next time.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/11442</link><guid isPermaLink="true">https://forum.netxms.org/post/11442</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 03 Oct 2013 21:09:27 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Wed, 02 Oct 2013 12:24:46 GMT]]></title><description><![CDATA[<p dir="auto">Have you created NDD's for AT switches yet? I am eagerly checking every ChangeLog since my last reply and haven't seen anything about AT.  <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forum.netxms.org/post/11425</link><guid isPermaLink="true">https://forum.netxms.org/post/11425</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Wed, 02 Oct 2013 12:24:46 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Tue, 04 Jun 2013 08:30:20 GMT]]></title><description><![CDATA[<p dir="auto">Just sent you two emails, one for each device, with hints on the MIB files along with few screenshots.<br />
I will send you similar information regarding other models of AT shortly.<br />
Im looking forward to new NDD's.</p>
<p dir="auto">Thanks,<br />
Iliyan</p>
]]></description><link>https://forum.netxms.org/post/10440</link><guid isPermaLink="true">https://forum.netxms.org/post/10440</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Tue, 04 Jun 2013 08:30:20 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Mon, 03 Jun 2013 20:53:56 GMT]]></title><description><![CDATA[<p dir="auto">Just send them to <a href="mailto:dump@netxms.org" rel="nofollow ugc">dump@netxms.org</a>, preferably with some comments on where to look for information about VLANs and physical ports.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/10437</link><guid isPermaLink="true">https://forum.netxms.org/post/10437</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 03 Jun 2013 20:53:56 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Mon, 03 Jun 2013 10:56:46 GMT]]></title><description><![CDATA[<p dir="auto">How can I send you these MIB files because apparently I can't attach it here due to file size limits?</p>
]]></description><link>https://forum.netxms.org/post/10432</link><guid isPermaLink="true">https://forum.netxms.org/post/10432</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Mon, 03 Jun 2013 10:56:46 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Mon, 03 Jun 2013 10:19:26 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">NetXMS server has "network device drivers" which handles all vendor/device specifics. As there are no standard MIBs for reading physical port information, "Ports" tab is blank for devices without drivers. It also can affect VLAN info display. If you can point me to appropriate MIBs for AlliedTelesis switches, I can create a driver and include it into next release.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/10427</link><guid isPermaLink="true">https://forum.netxms.org/post/10427</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 03 Jun 2013 10:19:26 GMT</pubDate></item><item><title><![CDATA[Reply to AlliedTelesis - network topology on Thu, 30 May 2013 07:17:27 GMT]]></title><description><![CDATA[<p dir="auto">Also when I to "Pull Topology" I'm getting this:</p>
<p dir="auto">[30.05.2013 10:15:43] **** Poll request sent to server ****<br />
[30.05.2013 10:15:43] Poll request accepted<br />
[30.05.2013 10:15:43] Starting topology poll for node AT48-FL4-Rack1-6<br />
[30.05.2013 10:15:43] VLAN list successfully retrieved from node<br />
[30.05.2013 10:15:46] Switch forwarding database retrieved<br />
[30.05.2013 10:15:46] Link layer topology retrieved (0 connections found)<br />
[30.05.2013 10:15:46] Updating peer information on interfaces<br />
[30.05.2013 10:15:46] Link layer topology processed<br />
[30.05.2013 10:15:46] Finished topology poll for node AT48-FL4-Rack1-6<br />
[30.05.2013 10:15:46] **** Poll completed successfully ****</p>
]]></description><link>https://forum.netxms.org/post/10408</link><guid isPermaLink="true">https://forum.netxms.org/post/10408</guid><dc:creator><![CDATA[vutoff]]></dc:creator><pubDate>Thu, 30 May 2013 07:17:27 GMT</pubDate></item></channel></rss>