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

Pages: 1 [2]
16
Some additional information...

I run the discovery process (nedi.pl -p) several times today - withou interruptions yet - so I assume, that the problem is fixed now.

Unfortunately, the backing up configs (nedi.pl -vA "login != ''" -bB -SsmgrfpitedobwaOA) is still interrupted by the "Resource temporarily unavailable at ./inc/libcli-iopty.pm line 871" problem.

Would it be possible to just ignore that error and continue with the next device? Or does anyone have any idea regarding the real cause of that problem?

17
Thx for the quick reply  :)

In general, backing up configs is working, but is also interrupted by the same error (Resource temporarily unavailable at ./inc/libcli-iopty.pm line 871).

I would like to keep the backup function available.

I changed the getfwd option from 'dyn' to 'snmp' and now it seems to work. I will monitor the hourly discovery scans and will report, whether it keeps running.






18
Some additional information:
The error happens on different device types - not just on WLAN Access Points.

Whenever I run Nedi discovery, it stops at a different device with the reported error.

I created subsets of my seed file and run the discovery process with these different subsets of the seed file and at every run, it stops at a different device - sometimes the discovery process manages to run through the complete seed file...

19
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?



20
Definition Files / Re: search def for WS-C2960S-24TS-L
« on: September 16, 2011, 05:31:24 PM »
Yes, I use 1.06  :)

The Typoid is in the .def file located in the /var/nedi/sysobj directory...

Code: [Select]
nedi01:/var/nedi/sysobj#more 1.3.6.1.4.1.9.1.1208.def
# Definition for 1.3.6.1.4.1.9.1.1208

# General
SNMPv   2HC
Type    WS-C2960S
Typoid  1.3.6.1.2.1.47.1.1.1.1.13.1001
OS      IOS
Icon    w2bn
Bridge  VLX
Dispro  CDP
Serial  1.3.6.1.4.1.9.3.6.3.0
Bimage  1.3.6.1.4.1.9.2.1.73.0

But unfortunately, for all of my 2960S switches, just "WS-C2960S" is displayed as type on the web page. Just in the module description, the correct switch type is listed like "WS-C2960S-48TS-L". But maybe that is what is expected?

When I look in the database, the 'Type' field of the device table is filled with "WS-C2960S"

Piet

21
Definition Files / Re: search def for WS-C2960S-24TS-L
« on: September 15, 2011, 01:39:19 PM »
Hi everybody,

we have lots of 2960S switches of different types (24 and 48 Port, with and without PoE option) in place, and unfortunately, because Cisco gives them just one OID (1.3.6.1.4.1.9.1.1208) it is not possible to separate the different types from each other.

I tried vtur's hint and I added "Typoid  1.3.6.1.2.1.47.1.1.1.1.13.1001" to the "1.3.6.1.4.1.9.1.1208.def", but it seems not to work.

I added the Typoid statement into the .def file from a termial session using VI
Code: [Select]
nedi:/var/nedi/sysobj#more 1.3.6.1.4.1.9.1.1208.def
# Definition for 1.3.6.1.4.1.9.1.1208

# General
SNMPv   2HC
Type    WS-C2960S
Typoid  1.3.6.1.2.1.47.1.1.1.1.13.1001
OS      IOS
Icon    w2bn
Bridge  VLX
Dispro  CDP
Serial  1.3.6.1.4.1.9.3.6.3.0
Bimage  1.3.6.1.4.1.9.2.1.73.0

Now, I rescanned such a switch and opened the 'Device Status' page for that switch again, but the Type is still a "WS-C2960S"

And now the strange thing...

If I open the "Defgen" now, the Typoid fild is empty!

If I add the SNMP id to the Typoid field an run an SNMPGet by clicking on the green arrow beside the field, I receive the correct switch type.

When I update and write the .def file from the Defgen Web page, the Typoid field is written, but the next time I open it again, the Typoid field is empty again - although the entry is still in the .def file.

When I rescan a 2960S switch, the Type is always the one which is configured in the 'Type' field of the .def file.
I tested already to remove the "Type" from the .def file, but without success.

Piet


22
Discovery / Re: SSH login into Cisco deviced
« on: September 02, 2011, 08:35:58 AM »
Hello Remo,

thank you very much for this broad hint  ;)

I just tested with the additional terminal sessions to see what's going on with input.log and output.log.

But now, it seems, that nedi does not try to login into the device at all  ???

I tested different command line options like
Code: [Select]
./nedi.pl -vdbt IPAddress and
Code: [Select]
./nedi.pl -vdba IPAddress or
Code: [Select]
./nedi.pl -vdbBa IPAddress
And I removed the different userids from the nedi.conf and keep just that one which is valid for the tested device - but the only CLI related output from nedi.pl is
Code: [Select]
Prepare (CLI)  ----------------------------------------------------------------
PREP:No working user

Nothing is looged in the input.log nor in the output.log

Do you have any idea what could cause this problem?

Thank you very much agagin for your support!


Piet


23
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

24
Other / Re: Layer 2 trace
« on: October 24, 2010, 01:21:36 PM »
Hello Remo,

that sounds very good  :)

An additional graphical view of the layer 2 route (Topology Map) through the network would be an extraordinary feature...

I am looking forward to 1oh6 and maybe you will find some time later for the layer 2 trace feature - if that would be a helpful feature for others too.

Thanx a lot again for that fantastic tool..

Piet

25
Other / Re: Layer 2 trace
« on: October 23, 2010, 06:24:33 PM »
I do not know, how the tool (it is 'What's up Gold') internally works.

I assume, that it retreives the layer 2 connections from the internal database - as NeDi could do it as well.

The input mask is very easy - just a drop down fild to select a source device and a second drop down field to select the target device. Then it displays the layer 2 route through the network form source to target as described in my initial post.

We use that feature for troubleshooting.

Piet

26
Other / Re: Layer 2 trace
« on: October 22, 2010, 12:14:01 PM »
No comments on this feature?

Nobody interested in? :(

27
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 [2]