Messages

1

Installation / Upgrade to NeDi 2.1 - API Error 401

« on: October 31, 2022, 09:15:20 am »

Hi,

After upgrading to NeDi 2.1 i get error 401 when attempting to access the API
https://<FQDN>/nedi/query.php?t=devices

ERR401:Invalid credentials!

SSH, GUI Auth is working fine, changing password doesn't help, any suggestions?

2

Definition Files / Cant edit .def files via GUI after 1.8 update.

« on: April 17, 2020, 10:32:45 am »

Hi,

After updating NeDi to 1.8 i can no longer edit the SysObjID on my devices via the NeDi GUI.

I can access the DefGenerator.

I get the following message:

Access Notice
You're not authorized for this!

On the files in SysObj:
# ls -l 1.3.6.1.2.1.33.def
-rwxrwxr-x 1 nedi apache 701 Apr 10  2018 1.3.6.1.2.1.33.def


And the module configuration in nedi.conf:'
¨
#============================================================================
# GUI Settings
#============================================================================

# Define the modules you wish to include in the menu and
# assign a group required for access
#       Section         Module                  Icon    Group
module  Devices         List                    dev     net
module  Devices         Modules                 cubs    net
module  Devices         Interfaces              port    net
module  Devices         Vlans                   vlan    net
module  Devices         Status                  sys     net
module  Devices         Config                  conf    net
module  Devices         Doctor                  info    net
module  Devices         Graph                   grph    net
module  Devices         Write                   wrte    adm

module  Assets          List                    list    oth
module  Assets          Management              pkg     mgr
module  Assets          Locations               home    oth
module  Assets          Loced                   ncfg    mgr

module  Topology        Table                   icon    net
module  Topology        Map                     paint   net
module  Topology        Routes                  rout    net
module  Topology        Multicast               cam     net
module  Topology        Spanningtree            traf    net
module  Topology        Networks                net     net
module  Topology        Links                   link    net
module  Topology        Linked                  ncon    mgr

module  Nodes           List                    nods    dsk
module  Nodes           Status                  node    dsk
module  Nodes           Toolbox                 tool    dsk
module  Nodes           RogueAP                 wlar    dsk
module  Nodes           Traffic                 tap     dsk
#module Nodes           PBX                     sms     dsk
#module Nodes           Create                  kons    adm

module  Reports         Devices                 ddev    net
module  Reports         Modules                 dcub    net
module  Reports         Interfaces              dif     net
module  Reports         Networks                dnet    net
module  Reports         Nodes                   dnod    dsk
module  Reports         Monitoring              dwrn    mon
module  Reports         Combination             dadd    mgr
module  Reports         Custom                  dcus    mgr


module  Monitoring      Health                  hlth    mon
module  Monitoring      Map                     map     mon
module  Monitoring      Events                  bell    mon
module  Monitoring      Timeline                news    mon
module  Monitoring      Incidents               bomb    mon
#module Monitoring      Master                  trgt    mon
module  Monitoring      Setup                   bino    adm

module  System          NeDi                    radr    mgr
module  System          Files                   file    adm
module  System          Database                db      adm
module  System          Services                cog     adm
module  System          Snapshot                foto    adm

module  User            Profile                 user
module  User            Management              ugrp    adm
module  User            Chat                    say
module  User            Logout                  exit

module  Other           Noodle                  find    oth
module  Other           Defgen                  geom    adm
module  Other           Calculator              calc    net
module  Other           Info                    php     oth
#module Other           Flower                  fan     oth
module  Other           Converter               hat2    oth
module  Other           Invoice                 cash
#module Other           Nagios                  cinf    oth


Best Regards
Andreas

3

Definition Files / Re: assistance with Palo Alto .def files

« on: April 09, 2020, 11:17:21 am »

Hello Rickli,
Could you please send me the def files package you are using for Palo Alto?

Thanks in advance.
Gaël

Hi Rickli, if you could share these it would be greatly appreaciated, im having some issues with authorization when going from NeDi 1.6 to NeDi 1.8 and will implementing our PA environment after.

4

Definition Files / Re: Help with .def files for Juniper EX-3400

« on: April 09, 2020, 11:14:18 am »

And the other attachment.

5

Definition Files / Help with .def files for Juniper EX-3400

« on: April 09, 2020, 11:13:59 am »

Hello Everyone!

I'm starting to more and more get the hang of NeDi but i have a problem with .def files for juniper modell ex-3400.

the .def files are similiar for 3200,3300 aswell as 3400 and i wouldnt need a change for it normally.

The problem is when listing slot modules and their descriptions.

EX-3300
jnxContentsDescr.7.1.0.0 = FPC: EX3300 48-Port @ 0/*/*
jnxContentsDescr.7.2.0.0 = FPC: EX3300 48-Port @ 1/*/*
jnxContentsDescr.7.3.0.0 = FPC: EX3300 48-Port POE+ @ 2/*/*
jnxContentsDescr.7.4.0.0 = FPC: EX3300 48-Port @ 3/*/*
jnxContentsDescr.7.5.0.0 = FPC: EX3300 48-Port @ 4/*/*

EX-3400
jnxContentsDescr.7.1.0.0 = FPC: EX3400-24P @ 0/*/*
jnxContentsDescr.7.2.0.0 = FPC: EX3400-24P @ 1/*/*
jnxContentsDescr.7.3.0.0 = FPC: EX3400-24P @ 2/*/*
jnxContentsDescr.7.4.0.0 = FPC: EX3400-24P @ 3/*/*
jnxContentsDescr.7.5.0.0 = FPC: EX3400-24P @ 4/*/*
jnxContentsDescr.7.6.0.0 = FPC: EX3400-24P @ 5/*/*
jnxContentsDescr.7.7.0.0 = FPC: EX3400-24P @ 6/*/*
jnxContentsDescr.7.8.0.0 = FPC: EX3400-24P @ 7/*/*
jnxContentsDescr.7.9.0.0 = FPC: EX3400-24P @ 8/*/*
jnxContentsDescr.7.10.0.0 = FPC: EX3400-24P @ 9/*/*

As you can see JunOS doesnt list the description properly, there is a way to display a different description with VC-member:

jnxVirtualChassisMemberModel.0 = ex3400-48p
jnxVirtualChassisMemberModel.1 = ex3400-48t
jnxVirtualChassisMemberModel.2 = ex3400-48t

And when i list the OiD 1.3.6.1.4.1.2636.3.40.1.4.1.1.1.8 it shows the proper modells, but now im not getting the serial numbers.

I listed 2 pictures, one is with the old OiD listing incorrect model but with serial, and the other is with the correct model but no serial, how can i change the descriptions without having serial nr removed? Or as it is not in the slot OiD this cant be done and i need to contact Juniper?

# Definition for 1.3.6.1.4.1.2636.1.1.1.4.131.2 created by Defgen 2.0 on 9.Apr 2020 (admin)
 
# Main
SNMPv   2HC
Type   EX3400
Typoid   
Sysdes   1.0.8802.1.1.2.1.3.4.0
OS   JunOS
Icon   w2ad
Size   1
TempAlert   
Bridge   qbriX
ArpND   
Dispro   LLDP
Serial   1.3.6.1.4.1.2636.3.1.3.0
Bimage   1.3.6.1.2.1.54.1.1.1.1.4.2
CfgChg   
CfgWrt   
FTPConf   
VLnams   1.3.6.1.2.1.17.7.1.4.3.1.1
VLnamx   1.3.6.1.4.1.2636.3.40.1.5.1.5.1.5
Group   
Mode   
 
# Interfaces
StartX   
EndX   
IFname   1.3.6.1.2.1.31.1.1.1.1
IFaddr   adr   
IFalia   1.3.6.1.2.1.31.1.1.1.18
IFalix   
InBcast   1.3.6.1.2.1.31.1.1.1.9
InDisc   1.3.6.1.2.1.2.2.1.13
OutDisc   1.3.6.1.2.1.2.2.1.19
IFvlan   
IFvlix   
IFpowr      
IFpwix   
IFdupl   1.3.6.1.2.1.10.7.2.1.19
IFduix   
Halfdp   2
Fulldp   3
 
# Modules
Modesc   1.3.6.1.4.1.2636.3.40.1.4.1.1.1.8
Moclas   1.3.6.1.4.1.2636.3.1.8.1.1
Movalu   3
Moslot   1.3.6.1.4.1.2636.3.1.8.1.6
Modhw   1.3.6.1.4.1.2636.3.1.8.1.7
Modsw   1.3.6.1.2.1.54.1.1.1.1.4.2
Modfw   1.3.6.1.4.1.2636.3.1.8.1.8.7
Modser   1.3.6.1.4.1.2636.3.1.8.1.7
Momodl   1.3.6.1.4.1.2636.3.1.8.1.10
Modloc   
Mostat   1.3.6.1.4.1.2636.3.1.8.1.7.7
Mostok   
 
# RRD Graphing
CPUutl   1.3.6.1.4.1.2636.3.1.13.1.8.7.1.0.0   
Temp   1.3.6.1.4.1.2636.3.1.13.1.7.7.1.0.0   
MemCPU   1.3.6.1.4.1.2636.3.1.16.0   -%
Custom      

6

Discovery / Re: SNMP - Juniper routing instance

« on: December 12, 2019, 02:36:56 pm »

SOLVED,

I've tought i might update here with the information.

When specifying RI@Community you only get the information from vlan and ports linked to this routing instance, wich in our case was non since it's linked via the default VLAN.

If specifying @Comunnity you get all the information without having to specify a routing-instance.. even-tough you can traverse via the routing-instance.


Referring to post below:
https://lists.gt.net/nsp/juniper/58135

7

Discovery / Re: SNMP - Juniper routing instance

« on: September 04, 2019, 11:55:24 am »

Also discovery gives this message, in regard to line 1752


10.X.X.X     901-Data@SYS-SW  v8Ix i6 RuRu(lo0)Ri(vlan.911)Ri(vlan)Ri(vlan.101)Ri(lo0.0)Ri(vlan.901)Use of uninitialized value in exists at /var/nedi/inc/libsnmp.pm line 1743.
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libsnmp.pm line 1752.
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libsnmp.pm line 1752.

8

Discovery / Re: SNMP - Juniper routing instance

« on: September 04, 2019, 11:14:01 am »

Hi again, i think i found something looking at the .def files

If i compare the same switches, 1 that is with our 1 ISP and then the new One i can see that the MIB information is diifferent, and they are linked to the same definition file, i've had a look at the Defgen tutorial and been able to reconfigure som switches that appear as red ones, but should i wait until every office has moved over to the new ISP before changing the def file or can i link it to 2 different def files?


OLD-ISP:
mib-2.17.1.4.1.2.4096: 514

New-ISP:
SNMPv2-SMI::mib-2.17.1.4.1.2.492: INTEGER: 526

Best regards
Andreas

9

Discovery / SNMP - Juniper routing instance

« on: September 04, 2019, 09:35:50 am »

Hello!

Recently our juniper EX series switches have moved over to a different ISP provider requiring us to set up an "routing-instance" in our switches for the layer 3 traffic forwarding.

This means that the default root routing isnt at a play when speaking to our server LAN and therefore don't have access to our NeDi client.
On our loopback interface we have an MGMT-IP wich is connected to the routing-instance from wich nedi will pull SNMP from, the only change in NeDi is the added IP-Adresses in netfilter and the adding of the vlan in the community config, like before it was public, but now it is 100-Data@Public where 100-Data is the routing-instance.


I get the MiB information from the switches but in NeDi only the Vlans and Loopback interfaces shows up and i cant see LLDP neighbours.

This also leads to a rather unpleasant 100-Data@SYS-SW01 name.

Has anyone experienced this before and can tell me if the problem is in the NeDi config och the SNMP config on the equipment?

I would suspect that there is both work needing to be done to connect default/root routing to the routing-instance in regards of the LLDP function, but as for "system name" i dont know if it's possible to configure it to not display the name of the routing-instance from the equipment or if it can be "hacked" away from NeDi Conf.

And if you cant tell im quite new to NeDi, much applies!

10

Discovery / Re: Dicovery - Netfilter error.

« on: July 02, 2019, 02:16:33 pm »

Ofcourse after a qiuck look at the documentation i found this, How can i exclude 10.99.99.X from being blocked by the netfilter?

11

Discovery / Dicovery - Netfilter error.

« on: July 02, 2019, 02:12:12 pm »

Hello !

This is my first post as a member of this forum.
I'm a freshly graduated IT-Operations technician with my focus in networking and surveillance.

We are switching over the a different ISP provider and have a new network configured.

When i add this network to the Seedlist along with the new community i get following error when running nedi.pl. (with the entire range ofcourse)

Could someone point me in the right direction here? SNMPwalk work's just fine.