Welcome, Guest. Please login or register.
Forums

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ageldenberg

Pages: [1]
1
Discovery / Re: Direct update MAC to IP address mapping
« on: March 11, 2019, 08:30:30 pm »
Rickli,

Thanks a lot for your comment.  If you can give me a sample of a sql command to update the table you mention, it would be great.

Regards,

Alek Geldenberg

2
Discovery / Direct update MAC to IP address mapping
« on: March 11, 2019, 08:02:32 pm »
Hello, NeDi gurus

Is there a way to update IP address of a specific MAC address directly in the database from a command line?

I may be able to use APIs to receive device information from Meraki cloud controller.  I can then use that information to update NeDi database with MAC-to-IP address mappings, if it is possible.

I will greatly appreciate your help.

3
Discovery / Re: Discovery of IP addresses of connected Nodes
« on: March 11, 2019, 01:45:16 pm »
In some cases the ARP tables are on Palo Alto firewalls.  Does anyone know how to get those into NeDi?  Is there a way to do it via SSH?

Thank you!

4
Discovery / Re: Discovery of IP addresses of connected Nodes
« on: March 07, 2019, 03:11:31 pm »
ShmuFoo

I believe you are correct.  The switches where IP addresses are not discovered are Layer2 switches.  Now, what can I do with those?  I do not know the inner working of NeDi.  To my mind it should use the ARP tables from the Layer3 switches and populate Layer2 switches with IP addresses.

I hope someone figured out how to find IP addresses of the devices connected to Layer2 switches.

5
Definition Files / Re: assistance with Palo Alto .def files
« on: March 07, 2019, 05:17:21 am »
PoodleCanon,

Have you figured out how to properly define .def files for Palo Alto devices?  Could you post them here?

Also, did you manage to figure out how to populate IP addresses of nodes connected to the devices.

Thank you very much.


6
Discovery / Discovery of IP addresses of connected Nodes
« on: March 07, 2019, 04:42:20 am »
Hello, NeDi gurus

I have a bunch of Cisco switches where I can see proper MAC addresses of connected nodes but no IP addresses.  Could you point me to the information on how those IP addresses can be discovered.  Do I need to tweak .def files or there are some other tricks.  I read that there is a way to populate MAC addresses from ARP tables via SSH.  How can I incorporate it into NeDi configuration?

Thanks a lot!

7
Discovery / Re: Support of Meraki Switches
« on: March 07, 2019, 04:32:52 am »
Posted .def files here:  https://forum.nedi.ch/index.php?topic=2205.0

8
Definition Files / Definition files for Meraki MS220-8P MS250-48FP MS350-48FP
« on: March 07, 2019, 04:32:05 am »
My NeDi installation could not get information about connected nodes from Meraki switches.  I tweaked a bit with defgen and as a result, with the following .def files, the MAC addresses of connected nodes are populated now.  However, most of the time the IP addresses are not displayed, so, my guess, the files need further work.  I will greatly appreciate any help.

9
Discovery / Re: Support of Meraki Switches
« on: March 05, 2019, 07:37:56 pm »
NeDi Gurus,

Could any of yo help me creating the .def file from the attached snmpwalk outputs (snmpwalk_meraki.txt - with translated OIDs and snmpwalk_meraki2.txt - with non-translated OIDs)?

I tried to do it via defgen screen, but it did not work.  I am trying to build it by comparing the structure of existing .def files with the outputs of snmpwalk. 

However, in the structure of .def file I did not find how to define OIDs to look for MAC addresses of connected devices. 

In the attached files the connected devices can be found by polling following OIDs:

.1.3.6.1.2.1.17.4.3.1.1.0.4.242.242.11.1 = STRING: 0:4:f2:f2:b:1
.1.3.6.1.2.1.17.4.3.1.1.0.27.23.0.35.16 = STRING: 0:1b:17:0:23:10
.1.3.6.1.2.1.17.4.3.1.1.0.27.23.0.35.18 = STRING: 0:1b:17:0:23:12
.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.10.115 = STRING: 0:72:78:df:a:73
.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.60.140 = STRING: 0:72:78:df:3c:8c
.1.3.6.1.2.1.17.4.3.1.1.40.41.134.10.198.6 = STRING: 28:29:86:a:c6:6
.1.3.6.1.2.1.17.4.3.1.1.52.86.254.28.105.112 = STRING: 34:56:fe:1c:69:70
.1.3.6.1.2.1.17.4.3.1.1.52.86.254.28.105.163 = STRING: 34:56:fe:1c:69:a3
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.71.71 = STRING: 64:16:7f:49:47:47
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.72.112 = STRING: 64:16:7f:49:48:70
.1.3.6.1.2.1.17.4.3.1.1.100.22.127.73.77.89 = STRING: 64:16:7f:49:4d:59
.1.3.6.1.2.1.17.4.3.1.1.112.11.79.122.5.16 = STRING: 70:b:4f:7a:5:10
.1.3.6.1.2.1.17.4.3.1.1.224.203.188.52.14.153 = STRING: e0:cb:bc:34:e:99
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.3.22.0 = STRING: e8:98:6d:3:16:0
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.0 = STRING: e8:98:6d:19:3:0
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.16 = STRING: e8:98:6d:19:3:10
.1.3.6.1.2.1.17.4.3.1.1.232.152.109.25.3.18 = STRING: e8:98:6d:19:3:12

As you can see the OIDs are constructed by converting MAC address of the device into decimal representation, starting from:  .1.3.6.1.2.1.17.4.3.1.1.

.1.3.6.1.2.1.17.4.3.1.1.0.114.120.223.10.115 = STRING: 0:72:78:df:a:73    (0=0.114=72.120=78.223=df.10=a.115=73)


In translated format it looks like this:

BRIDGE-MIB::dot1dTpFdbAddress.'......' = STRING: 0:4:f2:f2:b:1
BRIDGE-MIB::dot1dTpFdbAddress.'....#.' = STRING: 0:1b:17:0:23:10
BRIDGE-MIB::dot1dTpFdbAddress.'....#.' = STRING: 0:1b:17:0:23:12
BRIDGE-MIB::dot1dTpFdbAddress.'.rx..s' = STRING: 0:72:78:df:a:73
BRIDGE-MIB::dot1dTpFdbAddress.'.rx.<.' = STRING: 0:72:78:df:3c:8c
BRIDGE-MIB::dot1dTpFdbAddress.'()....' = STRING: 28:29:86:a:c6:6
BRIDGE-MIB::dot1dTpFdbAddress.'4V..ip' = STRING: 34:56:fe:1c:69:70
BRIDGE-MIB::dot1dTpFdbAddress.'4V..i.' = STRING: 34:56:fe:1c:69:a3
BRIDGE-MIB::dot1dTpFdbAddress.'d..IGG' = STRING: 64:16:7f:49:47:47
BRIDGE-MIB::dot1dTpFdbAddress.'d..IHp' = STRING: 64:16:7f:49:48:70
BRIDGE-MIB::dot1dTpFdbAddress.'d..IMY' = STRING: 64:16:7f:49:4d:59
BRIDGE-MIB::dot1dTpFdbAddress.'p.Oz..' = STRING: 70:b:4f:7a:5:10
BRIDGE-MIB::dot1dTpFdbAddress.'...4..' = STRING: e0:cb:bc:34:e:99
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:3:16:0
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:0
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:10
BRIDGE-MIB::dot1dTpFdbAddress.'..m...' = STRING: e8:98:6d:19:3:12

Going back to non-translated variant, the interfaces the devices are connected to are specified like this:

.1.3.6.1.2.1.17.4.3.1.2.0.114.120.223.10.115 = INTEGER: 14
.1.3.6.1.2.1.17.4.3.1.2.0.114.120.223.60.140 = INTEGER: 13
.1.3.6.1.2.1.17.4.3.1.2.40.41.134.10.198.6 = INTEGER: 38
.1.3.6.1.2.1.17.4.3.1.2.52.86.254.28.105.112 = INTEGER: 51
.1.3.6.1.2.1.17.4.3.1.2.52.86.254.28.105.163 = INTEGER: 51
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.71.71 = INTEGER: 21
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.72.112 = INTEGER: 17
.1.3.6.1.2.1.17.4.3.1.2.100.22.127.73.77.89 = INTEGER: 19
.1.3.6.1.2.1.17.4.3.1.2.112.11.79.122.5.16 = INTEGER: 1
.1.3.6.1.2.1.17.4.3.1.2.224.203.188.52.14.153 = INTEGER: 31
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.3.22.0 = INTEGER: 42
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.0 = INTEGER: 41
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.16 = INTEGER: 43
.1.3.6.1.2.1.17.4.3.1.2.232.152.109.25.3.18 = INTEGER: 39


INTEGER:42 means Port 42.

Please, advice if .def file can even be created in such a way that connected devices can be then consumed into the database.

Thanks a lot for help.

10
Installation / Re: Date in NeDi is 15 days in the future
« on: March 05, 2019, 06:56:27 pm »
Thank you, Rickli.  Updated date and time representation in my profile.  Worked like a charm.

11
Discovery / Re: Support of Meraki Switches
« on: March 05, 2019, 05:25:06 pm »
Rickli,

Is there a way to generate .def file from MIB file? Information: https://mibs.observium.org/mib/MERAKI-CLOUD-CONTROLLER-MIB/,  https://circitor.fr/Mibs/Html/M/MERAKI-CLOUD-CONTROLLER-MIB.php.  Could not upload the actual .mib file.

12
Installation / Re: Date in NeDi is 15 days in the future
« on: March 05, 2019, 03:46:20 pm »
Shame on me.  I am so used to American date format.  4.Mar 19  I thought it was "March 19".  Never mind the "4.".... Too much coffee. 

My apologies and thank you for your response.

13
Discovery / Re: Support of Meraki Switches
« on: March 05, 2019, 03:41:47 pm »
Rickli,

Would you, kindly, provide a link to Youtube video you mentioned?  I did not find it.  I will greatly appreciate that.

Thank you very much for your reply.


14
Installation / Date in NeDi is 15 days in the future
« on: March 04, 2019, 03:11:27 pm »
Hello, NeDi experts

For some reason NeDi does not utilize system's date.  I am running NeDi on Ubuntu server.  The system's date is correct, but the date in NeDi is about 15 days in the future.  Exmple:

Date: Mon Mar  4
Date in NeDi: Mar 19

Is there a configuration file, which I can tweak to fix the date?

Thank you!

15
Discovery / Support of Meraki Switches
« on: March 04, 2019, 01:47:15 pm »
Hello, NeDi community.

Has anyone been successful in recognizing nodes connected to Meraki switches?  I can see that the switches are being polled via SNMP properly.  However, nothing connected to those switches end up in the database.  Any help will be highly appreciated.


Pages: [1]