Welcome, Guest. Please login or register.

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 - big

Pages: [1] 2
1
Database / slow access
« on: October 02, 2017, 06:51:10 PM »
Hi Folks

Our nedi app seems to have developed an access issue. In many cases when I use the app
to get some device info it responds very quickly. However when I do an interface query the webserver takes forever, a very long time go get the results. I have to believe something is amiss.

I.E. IF name  like gi2/23 is horridly long.....

any ideas on where and how to troubleshoot? I looked at a couple of the system logs and really didn't see anything abnormal. that I could tell

it is a redhat OS 7.3

thanks in advance




2
Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: August 28, 2017, 03:52:03 PM »
attached are the defgens for a juniper  EX4300 and QFX5100
They work, but your mileage may very

3
Installation / Re: ocassional extra characters in snmp community string
« on: October 20, 2015, 02:59:22 PM »
activated ignore vlans.... lets see what we get


thanks


4
Installation / Re: ocassional extra characters in snmp community string
« on: October 15, 2015, 03:27:04 PM »
more info on this......

from my logs it looks like it might be a bug.

When I review the capture it appears every time that NeDI goes to the "legacy" vlans for the community string
using vlan 1002, 1003, 1004,1005 we get the authentication trap from the unit. These vlans do show in the "show vlan"
command but are legacy unless you actually have the cards.


5
Installation / Re: ocassional extra characters in snmp community string
« on: October 14, 2015, 06:56:51 PM »
thanks

my bad I didn't know this was a Cisco-ism.....
what I'm after is to find out why I get the the following errors in my syslog.
I fairly sure it is coming from nedi. I have to do more checking



10:42:02.795677 IP cacti.36068 > cm0515-502.snmp:  C=toucan@1 GetBulk(29)  N=0 M=25 17.1.4.1.2
10:42:02.797544 IP cm0515-502.snmp > cacti.36068:  C=toucan@1 GetResponse(475)  17.1.4.1.2.1665=49 17.1.4.1.3.1665=.0.0 17.1.4.1.4.1665=0 17.1.4.1.5.1665=0 17.2.1.0=1 17.2.2.0=
28673 17.2.3.0=853071200 17.2.4.0=1 17.2.5.0=00_01_7c_0e_ce_02_74_00 17.2.6.0=1 17.2.7.0=1665 17.2.8.0=2000 17.2.9.0=200 17.2.10.0=100 17.2.11.0=1500 17.2.12.0=2000 17.2.13.0=200 17.2.14.0=1500
17.2.15.1.1.1665=1665 17.2.15.1.2.1665=128 17.2.15.1.3.1665=5 17.2.15.1.4.1665=1 17.2.15.1.5.1665=1 17.2.15.1.6.1665=00_01_7c_0e_ce_02_74_00 17.2.15.1.7.1665=0
10:42:02.803136 IP cacti.60737 > cm0515-502.snmp:  C=toucan@1004 GetBulk(29)  N=0 M=25 17.4.3.1.2
10:42:03.053491 IP cm0515-502.55436 > cacti.snmptrap:  C=toucan Trap(102)  S:1.1.5 192.168.250.50 authenticationFailure 853634534 E:cisco.2.1.5.0=130.199.74.37 E:cisco.9.412.1.
1.1.0=1 E:cisco.9.412.1.1.2.0="130.199.74.37"
10:42:12.804941 IP cacti.60737 > cm0515-502.snmp:  C=toucan@1004 GetBulk(29)  N=0 M=25 17.4.3.1.2
10:42:13.057425 IP cm0515-502.55436 > cacti.snmptrap:  C=toucan Trap(102)  S:1.1.5 192.168.250.50 authenticationFailure 853635534 E:cisco.2.1.5.0=130.199.74.37 E:cisco.9.412.1.
1.1.0=1 E:cisco.9.412.1.1.2.0="130.199.74.37"


6
Installation / ocassional extra characters in snmp community string
« on: October 13, 2015, 10:16:04 PM »
Hi Folks

below is a sample of a problem I have found. It appears that nedi will occasionally add some characters to the community string.
it always is an @then numbers (see below) the real community string should be just community without any extra characters.
has anyone seen this behavior before? if so what is the problem? below is the tcpdump

thanks


IP nedi-server.55423 > cm0515-502.local.snmp:  C=community@556 GetBulk(38)  N=0 M=25 17.4.3.1.2.156.252.1.82.181.65
16:44:20.523594 IP cm0515-502.local.snmp > nedi-server.55423:  C=community@556 GetResponse(701)  17.4.3.1.2.156.252.1.99.207.41=1665 17.4.3.1.2.156.252.1.125.155.66=1665 17.4.3.1.2.156.252.1.
140.225.96=1665 17.4.3.1.2.156.252.1.195.115.136=1665 17.4.3.1.2.156.252.1.197.0.195=1665 17.4.3.1.2.156.252.1.200.94.205=1665 17.4.3.1.2.160.2.220.38.153.173=1665 17.4.3.1.2.160.2.220.130.240.1
13=1665 17.4.3.1.2.160.2.220.143.212.35=1665 17.4.3.1.2.160.24.40.50.21.9=1665 17.4.3.1.2.160.24.40.75.8.176=1665 17.4.3.1.2.160.24.40.171.243.158=1665 17.4.3.1.2.160.24.40.176.32.150=1665 17.4.
3.1.2.160.57.247.61.38.189=1665 17.4.3.1.2.160.57.247.68.64.116=1665 17.4.3.1.2.160.72.28.124.187.111=1665 17.4.3.1.2.160.72.28.130.182.25=1665 17.4.3.1.2.160.72.28.156.164.249=1665 17.4.3.1.2.1
60.136.180.13.27.104=1665 17.4.3.1.2.160.136.180.77.201.40=1665 17.4.3.1.2.160.136.180.140.27.244=1665 17.4.3.1.2.160.153.155.11.241.65=1665 17.4.3.1.2.160.153.155.12.124.73=1665 17.4.3.1.2.160.
153.155.21.232.187=1665 17.4.3.1.2.160.153.155.30.46.167=1665
16:44:20.529275 IP nedi-server.55423 > cm0515-502.local.snmp:  C=community@556 GetBulk(39)  N=0 M=25 17.4.3.1.2.160.153.155.30.46.167

7
Installation / Re: LDAP - AD Authentication
« on: August 13, 2015, 03:47:17 PM »


thanks
Glad you could confirm it.......

onward for me to test getting it to work with LDAP....
nedi is such a nice tool, glad to help with it


8
Installation / Re: LDAP - AD Authentication
« on: August 12, 2015, 09:04:02 PM »
Hi
I found what I think is a typeo in the inc/libldap.php file

the below is the modified function.... I now get network activity so I can try the next few steps on the LDAP server

more as we go


-------------------------------------------



function user_from_ldap_servers($login, $password = '', $import = true){
 
        global $ldapsrv, $user_dn, $fields; 
        global $dbhost,$dbuser,$dbpass,$dbname;
     
        // search if user exist in local user DB
                $link   = DbConnect($dbhost,$dbuser,$dbpass,$dbname);
                $query  = GenQuery('users','s','*','','',array(usrname'),array('='),array($login) ); // this line be array(usrname) NOT array(user) ??
                $res    = DbQuery($query,$link);

9
Installation / Re: LDAP - AD Authentication
« on: August 10, 2015, 08:31:27 PM »
thanks

when we go to 1.5 I'll give the LDAP / AD another try

10
Installation / LDAP - AD Authentication
« on: August 06, 2015, 05:00:59 PM »
Hi Folks

good morning

is there any documentation available on how to setup LDAP authentication for NeDi?
I am only looking to do user authentication not authorization via ldap
perhaps an example nedi.conf with comments about what is needed.

I want to query a Microsoft Domain Controller for the user.

any help appreciated.

11
Discovery / speeding up discovery
« on: June 08, 2015, 10:22:35 PM »
Hi Folks

another question if I may. Is it possible to speed up the discovery interval? right now I need about 2hrs do
discover everything on the network. I see a reference to "borders" but I don't see a configuration example
or much documentation on configuring this nedi.pl switch. Any one done this? if so can you share some specifics?

thanks

12
Discovery / Re: discovery and mac addresses
« on: May 27, 2015, 02:59:46 PM »
progress on the arista def. looks like I have it mostly working properly now.

I have run into one issue though. in the Device status display the interfaces all show vlan 0 on them. from the configuration of the unit
I know that is not correct. many of the interfaces are on access mode vlans. However, if you go to the Node List display for the same device name, the mac addresses and the CORRECT VLAN are displayed. Could this be another setting in the def file??????

13
Discovery / Re: discovery and mac addresses
« on: May 21, 2015, 08:52:35 PM »
thanks yup this helped......

I'll give you an updated arista defgen wit the correct setting.
Since I'm a newoob with this it terse going until you start figuring things out

14
Discovery / Re: discovery and mac addresses
« on: May 21, 2015, 02:37:10 PM »
in the log I get the following:

there is a mapping from IP to mac address so how do I get the macs and IP's into the nedi database?

is the last line the problem? ipNetToPhysical requested table is empty??????


ArpND (SNMP)   ----------------------------------------------------------------
SNMP:Connect 130.199.200.24 toucan v2 Tout:2s MaxMS:1472 Retry:1 NB:0
IP2M:b083fecea8ad on Vl202   1.1.1.2
IP2M:b083fed2897b on Vl200   1.1.1.3
IP2M:b083fecd5a2c on Vl202   1.1.1.4


ERR :ipNetToPhysical Requested table is empty or does not exist

Write ArpND --------------------------------------------------------

15
Discovery / discovery and mac addresses
« on: May 20, 2015, 11:08:57 PM »
Hi Folks

here is a good question I have run into. I just started setting up the def files for a new arista 7508 unit.
So far everything seems to get polled into nedi. However there are no MAC addresses for devices that are
attached to the arista interfaces in the nodes tables. Any idea how to get this functionality working

thanks


Pages: [1] 2