NetXMS Support Forum

Please login or register.

Login with username, password and session length

Author Topic: AlliedTelesis - network topology  (Read 6677 times)

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
AlliedTelesis - network topology
« on: May 30, 2013, 10:07:57 am »

Hello,

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?

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?

I have attached screenshots from the console.
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #1 on: May 30, 2013, 10:17:27 am »

Also when I to "Pull Topology" I'm getting this:

[30.05.2013 10:15:43] **** Poll request sent to server ****
[30.05.2013 10:15:43] Poll request accepted
[30.05.2013 10:15:43] Starting topology poll for node AT48-FL4-Rack1-6
[30.05.2013 10:15:43] VLAN list successfully retrieved from node
[30.05.2013 10:15:46] Switch forwarding database retrieved
[30.05.2013 10:15:46] Link layer topology retrieved (0 connections found)
[30.05.2013 10:15:46] Updating peer information on interfaces
[30.05.2013 10:15:46] Link layer topology processed
[30.05.2013 10:15:46] Finished topology poll for node AT48-FL4-Rack1-6
[30.05.2013 10:15:46] **** Poll completed successfully ****
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6451
    • View Profile
Re: AlliedTelesis - network topology
« Reply #2 on: June 03, 2013, 01:19:26 pm »

Hi!

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.

Best regards,
Victor
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #3 on: June 03, 2013, 01:56:46 pm »

How can I send you these MIB files because apparently I can't attach it here due to file size limits?
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6451
    • View Profile
Re: AlliedTelesis - network topology
« Reply #4 on: June 03, 2013, 11:53:56 pm »

Just send them to dump@netxms.org, preferably with some comments on where to look for information about VLANs and physical ports.

Best regards,
Victor
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #5 on: June 04, 2013, 11:30:20 am »

Just sent you two emails, one for each device, with hints on the MIB files along with few screenshots.
I will send you similar information regarding other models of AT shortly.
Im looking forward to new NDD's.

Thanks,
Iliyan
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #6 on: October 02, 2013, 03:24:46 pm »

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.  :)
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6451
    • View Profile
Re: AlliedTelesis - network topology
« Reply #7 on: October 04, 2013, 12:09:27 am »

Sorry, not yet. At some point I completely forgot about it :( I've added a bugtracker issue (https://www.radensolutions.com/chiliproject/issues/367) so it will not be forgotten next time.

Best regards,
Victor
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #8 on: October 04, 2013, 11:42:45 am »

Thanks. Btw, have you consider adding Mikrotik NDD as well?
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #9 on: February 04, 2014, 11:01:46 am »

First of all, thank you for unlocking the topic.

The AT NDD driver seem to work only partially.
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 .1.3.6.1.4.1.207.8.33.8. It will show this data:

# snmpwalk -c ******** -v 2c 10.7.0.6 .1.3.6.1.4.1.207.8.33.8
iso.3.6.1.4.1.207.8.33.8.1.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.1.1.1.102 = INTEGER: 102
iso.3.6.1.4.1.207.8.33.8.1.1.1.400 = INTEGER: 400
iso.3.6.1.4.1.207.8.33.8.1.1.2.1 = STRING: "Default VLAN"
iso.3.6.1.4.1.207.8.33.8.1.1.2.102 = STRING: "WiFi"
iso.3.6.1.4.1.207.8.33.8.1.1.2.400 = STRING: "Newell"
iso.3.6.1.4.1.207.8.33.8.1.1.3.1 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.1.1.3.102 = INTEGER: 102
iso.3.6.1.4.1.207.8.33.8.1.1.3.400 = INTEGER: 400
iso.3.6.1.4.1.207.8.33.8.1.1.4.1 = STRING: "1-2,4,6-16,22,25-48"
iso.3.6.1.4.1.207.8.33.8.1.1.4.102 = ""
iso.3.6.1.4.1.207.8.33.8.1.1.4.400 = STRING: "3,5,17-21,23-24"
iso.3.6.1.4.1.207.8.33.8.1.1.5.1 = ""
iso.3.6.1.4.1.207.8.33.8.1.1.5.102 = STRING: "16,47"
iso.3.6.1.4.1.207.8.33.8.1.1.5.400 = ""
iso.3.6.1.4.1.207.8.33.8.1.1.20.1 = INTEGER: 2
iso.3.6.1.4.1.207.8.33.8.1.1.20.102 = INTEGER: 2
iso.3.6.1.4.1.207.8.33.8.1.1.20.400 = INTEGER: 2
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.2 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.3 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.4 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.5 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.6 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.7 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.8 = INTEGER: 1
iso.3.6.1.4.1.207.8.33.8.2.1.1.1.9 = INTEGER: 1
...
...

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).
If needed I can provide access to my NetXMS installation so you can perform any kind of tests you like. Just let me know.

Regards,
Iliyan
Logged

Victor Kirhenshtein

  • Lead Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 6451
    • View Profile
Re: AlliedTelesis - network topology
« Reply #10 on: February 11, 2014, 01:49:16 am »

Access to real equipment can really help. Can you contact me directly so we can organize it?
Logged

Iliyan Vutov

  • Newbie
  • *
  • Posts: 21
    • View Profile
Re: AlliedTelesis - network topology
« Reply #11 on: February 11, 2014, 02:37:57 pm »

You've got a message.  :)
Logged

sarangtc

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: network topology
« Reply #12 on: September 09, 2018, 06:55:59 pm »

I have a similar issue with some dlink switches (not with netgear and cisco switches).

I get "VLAN list successfully retrieved from node"

[09.09.2018 20:54:13] **** Poll request sent to server ****
[09.09.2018 20:54:14] Poll request accepted
[09.09.2018 20:54:14] Starting topology poll for node Library
[09.09.2018 20:54:14] VLAN list successfully retrieved from node
[09.09.2018 20:54:20] Switch forwarding database retrieved
[09.09.2018 20:54:21] Link layer topology retrieved (1 connections found)
[09.09.2018 20:54:21] Updating peer information on interfaces
[09.09.2018 20:54:21] Link layer topology processed
[09.09.2018 20:54:21] Finished topology poll for node Library
[09.09.2018 20:54:21] **** Poll completed successfully ****

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)

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

.1.3.6.1.4.1.171.10.76.9.7.6.1

.iso.org.dod.internet.private.enterprises.d-link.dlink-products.dlink-DGS1210SeriesProd.dgs-1210-16ax.companyDot1qVlanGroup.dot1qVlanTable.dot1qVlanEntry
Logged