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

Pages: [1] 2
1
GUI / in-deep location plant
« on: August 28, 2014, 05:03:15 PM »
hi all.
Is there a way to see my device into a custom plant map? ie. set the position of the Access Point or the switches rack into an autocad plant so we can see where they are?
I'm able to position only the plant into a geo map, but cannot go "forward" and position the single device into a custom map

2
Definition Files / Re: Allied Telesis / Telesyn
« on: July 09, 2013, 08:43:25 AM »
you see a new LLDP part into web interface

3
Discovery / Re: LLDP with strange IP result
« on: July 09, 2013, 08:40:38 AM »
Definitively: it's works !!!!
tnx a lot

4
Discovery / Re: LLDP with strange IP result
« on: July 08, 2013, 10:07:57 AM »
Tnx
But I've got this code in that line..... cannot ficure how to insert those line in this code......
maybe I've don't have the last libsnmp.pm. But I have Neteye from whuert Phoenix, and i use their repository to upgrade Nedi..
Could you give me the part of code i need to insert? and not only the line number?


   1583                         while( my($key, $val) = each(%{$r}) ) {
   1584                                 my @k = split (/\./,$key);
   1585                                 my $x = ($dp =~ /LLDPX/)?$lix{$k[12]}:$k[12];
   1586                                 if($x){

edit: sorry the "irruence": i try to insert some line after, where "seem" to be the right place: (it's after 1594 row :)

   1592                                         }elsif($k[15] == 6){                                            # MAC (you never know!)
   1593                                                 my $mc   = sprintf "%02x%02x%02x%02x%02x%02x",$k[16],$k[17],$k[18],$k[19],$k[20],$k[21];
   1594                                                 &misc::Prt("LLDP:Ignoring MAC address $mc\n");
   1595                                         # --- Mod Inserted here ---
   1596                                         }elsif(@k == 19){                  # Phoenix Contact do it this way...
   1597                                                 $neb{$x}{$k[13]}{'ip'} = &misc::MapIp("$k[15].$k[16].$k[17].$k[18]");
   1598                                         # --- end mod ---

Seem Working.....

5
Discovery / Re: Cisco/HP mixed environment
« on: July 03, 2013, 01:01:51 PM »
So, try using CDP|LLDPXN or CDP|LLDPXA the only other 2 possibilities...
Of course, using only LLDP will brake every CDP link... no problem: it will be rebuild then




6
Discovery / Re: Cisco/HP mixed environment
« on: July 03, 2013, 11:49:02 AM »
We also have mixed Cisco/Hp/Allied Telesin in a site, and setting "CDP|LLDP" as discovery protovol into cisco definition file solve for us this discovery issue we have had.
so... using LLDP only in the definition file isn't the solution, but a good test to see what's NeDi do with your're cisco switches. 2 minutes work: change .def file, launch an ADD IP "verbose" from the web interface, see what's written in the logfile then revert back the definition file.


7
Discovery / Re: Cisco/HP mixed environment
« on: July 02, 2013, 03:42:20 PM »
Because you see HP switches in "sho LLDP nei" in HP switches, i'm pretty sure "CDP|LLDP" wasn't saved correclty into definition file.
If you re-edit it, did you see the strings? if not, you have just write it into editor, but not saved into .def file.
you could also check changing the definition file with only LLDP, and redo the test above

8
Discovery / Re: Cisco/HP mixed environment
« on: July 02, 2013, 02:26:07 PM »
you can manual add the IP of the  switches... (one cisco and one HP), add "verbose" but without protocol (faster). and see if you can see something into "DisProtocol  ----------------------" part.
NeDi should tell you LLDP or CDP result with the IP that should discovery if "protocol" were selected.

9
Definition Files / Re: Allied Telesis / Telesyn
« on: July 02, 2013, 08:34:37 AM »
I got some AT - 8000S
I created this .def file: it's incomplete but it give you some data.
AT8000S need to be updated to some recent (!!!??!!) firmware to activate the LLDP discovery protocol: all the ours was old and didn't support discovery until we didn't update them.

# Definition for 1.3.6.1.4.1.207.1.4.128 created by Defgen 1.8 on 2.Jul 2013 (xxxx)

# General
SNMPv   2
Type   AT-8000S 48port
Typoid   
Sysdes   1.3.6.1.2.1.1.1.0
OS   other
Icon   w2yd
Size   1
Bridge   normal
ArpND   oldphy
Dispro   LLDP
Serial   1.3.6.1.2.1.17.1.1.0
Bimage   

# Vlan Specific
VLnams   
VLnamx   
Group   
Mode   

# Interfaces
StartX   
EndX   
IFname   1.3.6.1.2.1.31.1.1.1.1
IFaddr   oldadr
IFalia   1.3.6.1.2.1.31.1.1.1.18
IFalix   
InBcast   
InDisc   1.3.6.1.2.1.2.2.1.13
OutDisc   1.3.6.1.2.1.2.2.1.19
IFvlan   1.3.6.1.2.1.17.7.1.4.5.1.1
IFvlix   
IFpowr      
IFpwix   
IFdupl   1.3.6.1.2.1.10.7.2.1.19
IFduix   1.3.6.1.2.1.10.7.2.1.1
Halfdp   2
Fulldp   3

# Modules
Modesc   1.3.6.1.2.1.47.1.1.1.1.2
Moclas   1.3.6.1.2.1.47.1.1.1.1.5
Movalu   9
Moslot   1.3.6.1.2.1.47.1.1.1.1.7
Modhw   
Modsw   1.3.6.1.2.1.47.1.1.1.1.9
Modfw   1.3.6.1.2.1.47.1.1.1.1.10
Modser   
Momodl   

# RRD Graphing
CPUutl   
Temp      
MemCPU      
Custom      

10
Discovery / Re: LLDP with strange IP result
« on: July 01, 2013, 06:29:23 PM »
I send you a private message with the info some days ago.... then, I went to  holiday :)

11
Discovery / Re: Cisco/HP mixed environment
« on: July 01, 2013, 06:27:08 PM »
you need to change the definition file for the cisco and modify CDP protocol with CDP|LLDP (i do this solution), or, if the link for HP switches is unique (or very few), you can add the HP in the seedlist: the HP will be added, then, LLDP will discovery the Cisco and the link will be added.

12
Discovery / LLDP with strange IP result
« on: June 19, 2013, 05:44:55 PM »
Hi.
I got some (new) industrial switches to monitor coming from Phoenix Contact.
LLDP was enable and I create the .def file.
Anyway, discovery wasn't work:
LLDP seem to work, it discover the 2 similar neighbor but it takes a strange IP as result: so link was addedd, but further switches wasn't discovered:
If i add by hand all switches, I can also see every right connection.
I will cut/paste (little modified) the log of discovery:


DisProtocol  ------------------------------------------------------------------
SNMP:Connect xx.xx.6.240 public v2 Tout:7s MaxMS:4095
LLXN:6 index 6 is IF index 6
LLXN:3 index 3 is IF index 3
LLXN:8 index 8 is IF index 8
LLXN:7 index 7 is IF index 7
LLXN:4 index 4 is IF index 4
LLXN:2 index 2 is IF index 2
LLXN:5 index 5 is IF index 5
LLXN:1 index 1 is IF index 1
ERR :LLDP PoE Requested table is empty or does not exist
LLDP:ASCII address ��
LLDP:ASCII address ��
LLDP:xxxx_SW24 _1       on 1        ��             Switch_2 ( Switch_2 (L) Se
LLDP:Queueing of xxxx_SW241 is ok
LLDP:xxxx_SW24 _1       on 2        ��             Smart Mana Smart Managed C
LLDP:Queueing of xxxx_SW244 is ok



Discover     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Identify xxxx_SW241 -------------------------------------------------------
SNMP:Connect �� othercomm v2 Tout:2s MaxMS:1472
SNMP:Connect �� public v2 Tout:2s MaxMS:1472
EVNT:CL=nedn EL=1 TGT=xxxx_SW241 MSG=No response from IP �� using -a xx.xx.6.240
DISC:ToDo/Done-Time                        1/1-0s

Discover     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Identify xxxx_SW244 -------------------------------------------------------
SNMP:Connect �� othercomm v2 Tout:2s MaxMS:1472
SNMP:Connect �� public v2 Tout:2s MaxMS:1472
EVNT:CL=nedn EL=1 TGT=xxxx_SW244 MSG=No response from IP �� using -a xx.xx.6.240
DISC:ToDo/Done-Time                        0/1-0s
===============================================================================

13
Discovery / Re: About MSM controlled AP CDP discovery
« on: June 19, 2013, 02:26:17 PM »
after the discovery of the query, in Nedi, I'd prefer solve problem here.
We have planned to have 3 MSM760, and only one site have the Mixed arch: other site have all Cisco or All HP, but same AP connected to different controller: too caothics to solve the problem IN Access point word:
I think i will solve the problem better with query inside nedi.
Could be a good feature the ability to save your own queries inside Nedi and the ability to schedule directly.
Maybe, directly as text into configuration file :)


14
GUI / Re: date of last interface input counter change
« on: June 14, 2013, 02:15:01 PM »
reply to this post... I thinks there's a little bug on the lastchg field in the interface view.
I see different value of the last interface change depending the switch view and interfaces view.
Into switch views, i see a correct value; many of same interfaces, give me  "1 jan 70" into interfaces view.
there's no rules: in the same switch some interface are changed days ago, some few hours.

15
Discovery / Re: About MSM controlled AP CDP discovery
« on: June 13, 2013, 04:41:11 PM »
At the moment, I found a workaround running this query after the discovery process.
This will change the neighbor name in the links table, from serial to the device name into devices table, linked with serial.
This works for my AP, in my environmen: I think it's not for everyone..... anyway, every rediscovery time, links will be rebuild, so nothing was lost.
There's some little problem: some AP was discovered twice or tree time, from different switch by LLDP and CDP and results was not correct....




UPDATE
links,devices
SET
links.neighbor = devices.device
where
(links.neighbor = devices.serial ) and
(devmode = 16 or devmode = 15)


Pages: [1] 2