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 - Hannu Liljemark

Pages: [1] 2 3 ... 8
1
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« on: August 03, 2017, 01:52:31 PM »
Quote
IfAddresses  ------------------------------------------------------------------
IFIP:No useip policy set, always using discovered IPs
SNMP:Connect 172.18.0.222 public v2 Tout:2s MaxMS:1472 Retry:1 NB:0
IFIP:Walking ifaddress table
ERR :ifAddressTable The requested table is empty or does not exist

DisProtocol  ------------------------------------------------------------------
SNMP:Connect 172.18.0.222 public v2 Tout:7s MaxMS:4095 Retry:1 NB:0
ERR :LLDP nbr The requested table is empty or does not exist

Modules      ------------------------------------------------------------------
SNMP:Connect 172.18.0.222 public v2 Tout:2s MaxMS:1472 Retry:1 NB:0
MOD :Walking module description
ERR :Description The requested table is empty or does not exist

In Defgen check the ARP/ND and try the different methods to see which mechanism your switch supports for IfAddresses.

Same for DisProtocol - can you get any data from the switch if you try CDP, FDP or NDP? You may have to investigate the switch CLI or manuals to see if it supports LLDP/CDP even there.

Modules section is near the bottom of Defgen. I guess the defaults are for devices that support ENTITY-MIB. It may be that Raisecom doesn't support that... yet another thing to investigate.

If there's any publicly available MIB file available from Raisecom or in google, you might want to look at that and see if there's anything useful that could be used to pull the data.

Not all devices have support so you may be left without e.g. module or neighbour data.

I guess you can do this also in NEDIO: go to the OS using ssh, find nedi/sysobj directory and do:

grep Modesc * | awk '{print $2}'|grep -v '^$'|sort -u

Here there's currently 38 different OIDs one can use to pull module descriptions depending on device vendor, model and possible even software version. So, either Raisecom supports one of those, or there's something completely new OID which you need to find, or you can just leave the module section empty so Nedi doesn't try to poll the data if it's not available :)

Br,
Hannu

2
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« on: August 03, 2017, 11:49:27 AM »
Okay, in that case I think the regexp should be modified to something like:

$cmd{'RaisecomOS'}{'ropr'} = '[\w.-]+>\s?$';
$cmd{'RaisecomOS'}{'enpr'} = '[\w.-]+#\s?$';

There's the \s removed since there's no whitespace between the hostname and the > or # part in the prompt.

Try that and then run the config backup again.

3
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« on: August 02, 2017, 11:46:49 AM »
Hi

If you simply login using telnet/putty, what does the switch prompt look like right after you've entered username and password? Does the prompt you see match the regexp you're using:

$cmd{'RaisecomOS'}{'ropr'} = '[\w.-]+\s>\s?$';
$cmd{'RaisecomOS'}{'enpr'} = '[\w.-]+\s#\s?$';

Sometimes the switch gives you full access after entering username and password, and it's not necessary to do "enable". For those cases you can see in libcli.pm for example:

$cmd{'FortiOS'}{'ropr'} = 'GitsDoNid';
$cmd{'FortiOS'}{'enpr'} = '[\w+().-]+\$\s?$';

There is no "$cmd{'FortiOS'}{'enab'} = 'enable';" because after login you have all the privileges you need.

So, I wonder how these Raisecom devices behave, if they require you to use a enable-like command or if you can do the "show startup-config" right after entering login and password? That will affect what you need for RaisecomOS in libcli.pm.

Br,
Hannu

4
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« on: August 01, 2017, 06:17:31 AM »
Have you tried looking into adding the support yourself? It's good fun to learn, and involves modifying libcli.pm and Other-Defgen.php. Here's an example where I added support for Extreme Network's wireless controller: http://forum.nedi.ch/index.php?topic=1957.msg7931#msg7931

Also http://forum.nedi.ch/index.php?topic=2038.0 is a good discussion from few months back.

Br,
Hannu

5
Thanks, Remo! Makes sense.

6
Hmm... that's an PHP extension, right? I'm seeing these while doing discovery with nedi.pl.

8
Uhhuh... basics work great with tristanbob's tips but funky things happen on Ubuntu 16, where both 1.4 and 1.5C are logging weird stuff. All was fine on Ubuntu 12/14.

CISCO887VA-M-K9 device:

DBD::mysql::st execute failed: Out of range value for column 'dinbrc' at row 1 at /var/nedi/inc/libdb.pm line 1342.
DBD::mysql::st execute failed: Out of range value for column 'dinbrc' at row 1 at /var/nedi/inc/libdb.pm line 1342.

Can't reproduce this anymore... maybe just some glitch in the middle of 1.5C update:

DBD::mysql::db do failed: Data too long for column 'device' at row 1 at /var/nedi/inc/libdb.pm line 1849.
DBD::mysql::db do failed: Data too long for column 'device' at row 1 at /var/nedi/inc/libdb.pm line 1849.

Maybe a long name for wlan client pulled from Cisco WLC 5508:

DBD::mysql::db do failed: Data too long for column 'noduser' at row 1 at ./inc/libdb.pm line 2081.
DBD::mysql::db do failed: Data too long for column 'noduser' at row 1 at ./inc/libdb.pm line 2081.

For now I'll just mapip few devices to 0.0.0.0 until I figure this out.

----
Caught one issue with debugging:

EVNT:MOD=1/1 L=200 CL=lnbi TGT=abc-abcd-123456789-abc-gw MSG=Fa0 ABCD has had 23860929 inbound broadcasts/s, exceeds alert threshold of 100/s!
DBG :INSERT INTO events (level,time,source,class,device,info) VALUES (200,1499336259,'abc-abcd-123456789-abc-gw','lnbi','abc-abcd-123456789-abc-gw','Fa0 ABCD has had 23860929 inbound broadcasts/s, exceeds alert threshold of 100/s!')
DBG :INSERTED 1 ROWS
DBD::mysql::st execute failed: Out of range value for column 'dinbrc' at row 1 at /var/nedi/inc/libdb.pm line 1342.
DBD::mysql::st execute failed: Out of range value for column 'dinbrc' at row 1 at /var/nedi/inc/libdb.pm line 1342.

DBG :UPDATE nodes SET lastseen=1499337254,device='AP_AB_CDEF_12',ifname='Do0',vlanid=1,ifchanges=687,metric='SHHSHSHTH',noduser='host/AB-CDE-FGHIJKLM.abcde.efghijkl.fi' WHERE mac='54e1ad07cfb4'
DBD::mysql::db do failed: Data too long for column 'noduser' at row 1 at ./inc/libdb.pm line 2081.
DBD::mysql::db do failed: Data too long for column 'noduser' at row 1 at ./inc/libdb.pm line 2081.

Br,
Hannu

9
Discovery / Re: Switch Planet
« on: May 12, 2017, 07:10:23 PM »
Couple of years ago I added support for Extreme Networks wireless controller, and here's reference to what I did back then: http://forum.nedi.ch/index.php?topic=1957.0

Br,
Hannu

10
Discovery / Re: Switch Planet
« on: May 12, 2017, 12:25:41 AM »
Hi

perhaps there's no support for that brand of switches at the moment. If that's the case then you should watch Remo's defgen tutorial youtube video linked on the http://www.nedi.ch/documentation/expand/ page to get started.

Planet CLI guide (I found it from http://ftp.asm.cz/Planet/VIP-100T/Manual/EM_VIP100TCLIV1.pdf) seems to say 'sysconf -print' is used to print the configuration. I doubt there's any other vendor with that syntax, so you need to add a new OS type to use the right CLI commands for config backup.

Br,
Hannu

11
Definition Files / C2960P24TcL and C2960P24TcS
« on: April 25, 2017, 03:21:28 PM »
Hey

Version 1.5.225p3 didn't seem to have these so here goes:

1.3.6.1.4.1.9.1.1757.def ciscoWsC2960P24TcS
1.3.6.1.4.1.9.1.1752.def ciscoWsC2960P24TcL

Br,
Hannu

12
Definition Files / Re: Cisco 3850 stack def
« on: November 18, 2016, 12:22:36 PM »
Oh, cool. I think yours is probably better!

Only thing is that the boot image OID reports "STRING: "flash:packages.conf" " on this stack that I have access to :) And module class I kept 3|6|10 as 9 reports both the switches on the stack but not serial numbers so I didn't think it was useful info. Maybe also collecting 9 class modules is handy for some reports...

13
Discovery / Re: Dot (.) in hostname
« on: November 18, 2016, 09:01:03 AM »
This doesn't really help you but I've had in our notes ever since we started using Nedi (before 1.4) that using a dot in hostname is a no-no. Cisco APs have dot in their name by default and Nedi has always screwed up the names if e.g. a freshly installed AP is in the network for a while and Nedi picks it up. To me having a dot in the hostname sounds bizarre if you think about fqdn.

Br,
Hannu

14
Definition Files / Cisco 3850 stack def
« on: November 17, 2016, 11:09:48 AM »
Here's a definition for Cisco 3850 stack, 1.3.6.1.4.1.9.1.1745.

Br,
Hannu

15
Definition Files / Re: Def for HP2920 stack
« on: May 06, 2016, 02:01:37 PM »
Ah, okay... gotcha.

So I might just as well poll either 1.3.6.1.2.1.99.1.1.1.4.112001 or .1.3.6.1.2.1.99.1.1.1.4.212001 to get temp from one of the switches in the stack :) At least I'll get some graph :)

Br,
Hannu

Pages: [1] 2 3 ... 8