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.


Topics - piet

Pages: [1]
1
Discovery / CLI access fail on 20% of my switches
« on: March 14, 2017, 08:24:00 AM »
Hello Forum,

I run NeDi 1.5.225p3 on Ubuntu 16.04 with PHP 5.6.30 and MySQL 5.7

In general, this system runs as expected.

But for approx. 20% of my switches (all Cisco) the configuration backup fails with errror
Code: [Select]
Prepare (CLI) ----------------------------------------------------------------
SSH :admin@10.10.10.23:22 Tout:2s OS:IOS EN:[\w+().-]+#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l admin 10.10.10.23
ERR0:pattern match timed-out
EVNT:MOD=B/1 L=150 CL=cfge TGT=SWITCH23 MSG=Config backup error: connection pattern match timed-out

I set
Code: [Select]
usessh always in nedi.conf.

The failing device types are different, i.e. WS-C3750-24FS-S (IOS 12.2(53)SE2), WS-C2960-24PC-L (IOS 12.2(53)SE2), WS-C3560G-24TS-S (IOS 12.2(53)SE2).

I tried to run nedi.pl in debug mode (/var/nedi/nedi.pl -v -d -b -a 10.10.10.23) to get additional information with input.log and output.log, but I could not get these files being created. I run the nedi.pl command as user www-data.

Does anybody has any hint how to fix this isse or at least how to get input.log and output.log being created?

Many thanks

piet



2
NeDiO / Fresh NoDiO14 installation - Network rrds are empty
« on: March 03, 2015, 08:13:03 AM »
Hello Forum,
in my fresh installed NeDiO14, the network rrds are empty - i.e. on the "Monitoring Health" page as well as in "Device Graphs/Network Totals".

The rrds of a single device are all ok.

piet

3
Discovery / Error messages during discovery
« on: May 07, 2013, 11:31:39 AM »
Hello Forum,

first of all a really big 'Thank you' to Rickly for thie new NeDi release  :)

I performed a fresh install of NEDIO8.

Unfortunately the following errors occur during discovery process:

After the discovery process of the devices, nedi says:
Building nodes
ooioonoUse of uninitialized value in gethostbyaddr at /var/nedi/inc/libmisc.pm line 1191.

I receive many of these messages.

After these message I recive many of the following lines:
Argument "NODENAME" isn't numeric in pack at /var/nedi/inc/libmisc.pm line 554.


Any idea what can cause thise problem?

Piet



4
Discovery / Network Discovery problem with 1.0.7
« on: February 13, 2012, 02:12:06 PM »
Hi Remo,

thank you so much for the new release  :)

Unfortunetly I have problems during the discovery process.

I use a fresh system install using the NeDiO7 ISO image and I did not copy any data, except some settings in the nedi.conf and my seedfiles.

When starting the new discovery process (using nedi.pl -p -u seedfile) I get the following message for each discovered device
Code: [Select]
Use of uninitialized value in concatenation (.) or string at /var/nedi/inc/libcli-iopty.pm line 479.and at the end, the discovery process crashes with the message
Code: [Select]
Resource temporarily unavailable at /var/nedi/inc/libcli-iopty.pm line 919. :(

Do you have any idea what could cause that problem?

Piet

5
Hello Forum,

I run Nedi 1oh6 on NEDIO6 (OpenBSD)

Since a while, the hourly discovery process (nedi.pl -p) stops with the error

Resource temporarily unavailable at ./inc/libcli-iopty.pm line 871.

The device where Nedi stops is always a Cisco 1242 WLAN AP running IOS (NOT WLAN Controller based).


I tried already to reinitialize the Nedi database, but without success.

Nedi stops not always at the same device, but it is always a 1242 WLAN AP.

If I run Nedi with -vd option, I receive the following output:

Code: [Select]
Discover     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Identify     ------------------------------------------------------------------
SNMP:Connect IPAddress ROCommunity v2 Tout:2s MaxMS:1472
IDNT:Name = Device
IDNT:New Device with ID seed120 and IP IPAddress found
IDNT:Testing write access with 1.3.6.1.2.1.11.30.0 set to 2
SNMP:Connect IPAddress ROCommunity v2 Tout:2s MaxMS:1472
ERR :Writetest, Received noAccess(6) error-status at error-index 1
SNMP:Connect IPAddress RWCommunity v2 Tout:2s MaxMS:1472
IDNT:Writetest set to 1 OK
IDNT:Writetest restore 2, using RWCommunity v2
SYS :Con=IT Loc=Germany
SYS :OS=IOS-wl SV=2 TY=AIR-AP1240

Enterprise   ------------------------------------------------------------------
SNMP:Connect IPAddress ROCommunity v2 Tout:2s MaxMS:1472
SERN:Serial number = FCZxyz
BOOT:Image = c1240-k9w7-mx.124-10b.JA3
CPU :Utilization = 0%
MEM :Available memory 6402272Bytes
TEMP:Environment = 0 Degrees Celcius

Interfaces   ------------------------------------------------------------------
SNMP:Connect IPAddress ROCommunity v2 Tout:7s MaxMS:2048
IF  :Getting HC counters
IF  :   ID:Name Spd Dup St Vl Description Alias PoE
IF  :    1:Do0         54Mb  ?  3  Vl0    Dot11Radio0                     0W
IF  :    2:Do1         54Mb  ?  0  Vl0    Dot11Radio1                     0W
IF  :    3:Fa0        100Mb  FD 3  Vl0    FastEthernet0                   0W
IF  :    4:Nu0      10000Mb  -  3  Vl0    Null0                           0W
IF  :    5:Do0.3       54Mb  -  3  Vl0    Dot11Radio0.3                   0W
IF  :    6:Do0.47      54Mb  -  0  Vl0    Dot11Radio0.47                  0W
IF  :    7:Fa0.3      100Mb  -  3  Vl0    FastEthernet0.3                 0W
IF  :    8:Fa0.47     100Mb  -  3  Vl0    FastEthernet0.4                 0W
IF  :    9:Fa0.52     100Mb  -  3  Vl0    FastEthernet0.5                 0W
IF  :   10:BV1         54Mb  -  3  Vl0    BVI1                            0W

IfAddresses  ------------------------------------------------------------------
IFIP:No useip policy set, always using discovered IPs
SNMP:Connect IPAddress ROCommunity v2 Tout:2s MaxMS:1472
IFIP:BV1      IPAddress    255.255.255.0   ok & unique

DisProtocol  ------------------------------------------------------------------
SNMP:Connect IPAddress ROCommunity v2 Tout:7s MaxMS:4095
CDP :Device2 Gi1/0/ on Fa0    IPAddress     cisco WS-C Cisco IOS Softw
CDP :Queueing Device3, already done

Modules      ------------------------------------------------------------------
SNMP:Connect IPAddress ROCommunity v2 Tout:2s MaxMS:4095
MOD :4 FastEthernet0 no class or no info
MOD :1 AP1240 class 3 no match with /10/ or no info
MODA:3-Dot11Radio1 802.11A Radio ALP122915TH
MODA:2-Dot11Radio0 802.11G Radio GAM122915TH

Prepare (CLI)  ----------------------------------------------------------------
SSH :admin;1:22 Tout:2s OS:IOS-wl EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l admin IPAddress
Resource temporarily unavailable at ./inc/libcli-iopty.pm line 871.

Does anyone have any idea?



6
Discovery / SSH login into Cisco deviced
« on: August 31, 2011, 10:57:11 AM »
Hello Forum,

I run the latest nedi1.0.6 on NEDIO6 and I have problems with ssh login into cisco devices.

A
Code: [Select]
./nedi.pl -vdbt IPAddress gives
Code: [Select]
SSH :admin:22 Tout:2s OS:IOS EN:(.+?)#\s?$
PTY :Forking ssh -o 'StrictHostKeyChecking no' -l admin IPAddress
CLI2:Matched Password:, sending password
CLI3:Password sent
CLI3:Matched Password:, login failed

The password contains special characters like # and - and $ and I assume, that the password might not taken correctly from the nedi.conf.

How can I check, which password is transfered to the device?

If I run
Code: [Select]
ssh -o 'StrictHostKeyChecking no' -l admin IPAddress manually and enter the password, the login works.

Thank you very much for your support  :)

Piet

7
Other / Layer 2 trace
« on: October 01, 2010, 09:22:12 AM »
Hello Nedi Fans,

first of all I would like to thank you for this fantastic tool.

I replace more and more of the network management tools by Nedi.

But in a different tool, I use an interesting feature, which could maybe integrated into a future release of Nedi?

They call it 'Layer 2 Trace'. Functionality of this feature is, to get the path through the network from one node to another.
You can select a source node and a destination node an the result is a table displaying the layer 2 path through the network.

To make it clearer, here is an example for such a table

Device   IP Address   Interface Name
SourceDevice.test.local   192.168.1.10   65539 - Vmware PCI Ethernet Adapter
AccessSwitch01.test.local   192.168.1.20   Gi0/12
AccessSwitch01.test.local   192.168.1.20   Gi0/20
DistributionSwitch01.test.local   192.168.1.30   Gi2/0/5
DistributionSwitch01.test.local   192.168.1.30   Gi1/4/21
BackBoneSwitch02.test.local   192.168.1.52   Gi1/3/12
BackBoneSwitch02.test.local   192.168.1.52   Gi2/1/15
DistributionSwitch02.test.local   192.168.1.33   Gi1/0/17
DistributionSwitch02.test.local   192.168.1.33   Gi1/2/21
AccessSwitch04.test.local   192.168.1.49   Gi0/10
AccessSwitch04.test.local   192.168.1.49   Gi0/16
DestinationDevice.test.local   192.168.1.64   1 - ln0

I think, the information to create such a table is already in the database. Maybe it is not too difficult, to implement such a feature?

What do the others think about that? Would that be a helpful feature for others too?

Piet

Pages: [1]