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

Pages: [1] 2 3 ... 7
1
Definition Files / Re: 3650 Bootimage OID
« on: August 04, 2015, 04:20:40 PM »
Just in case someone is interested. The issue was that someone used install mode for the affected devices.

2
Definition Files / 3650 Bootimage OID
« on: June 19, 2015, 09:55:37 AM »
Hi all,

does anyone have a better option than 1.3.6.1.4.1.9.9.249.1.1.1.1.5.1000 for the bootimage on the Cisco 3650 (1.3.6.1.4.1.9.1.1830/ 1.3.6.1.4.1.9.1.1826)?
I can't seem to find an OID showing the bin file, like 1.3.6.1.4.1.9.2.1.73.0 does e.g. on the 4500s.

Thanks.

3
News / Re: NeDi 1.0.9 Progress
« on: August 07, 2013, 02:50:43 PM »
So the right way is to save only the saved configuration, not the running one.
Another "crazy" idea: what about a section for additional commands that will be run against the switches and stored in the database like the config?
One could save startup and running configs then and even compare them over a huge amount of devices via SQL. "Which config has not been saved yet and how does the diff look like".

Similar things would be possible for any command.

4
News / Re: NeDi 1.0.9 Progress
« on: August 01, 2013, 02:48:35 PM »
  • Population per device
  • Free access ports (not used for 30 (or whatever is set as retire) days)
  • Whether a config was written after changes and it's backed up (including size and changes). Note that in the list below, I'm filtering on devices which actually support reading config status (write not equal change timestamp)
These are very nice ones. If we could set a threshold for "less ports available than desired" and log this in events, it would be awesome.

One more suggestion to recognize root causes of not discovered devices. Can we differentiate:
- not available devices (no reply on ping)
- SNMP access broken (currently says "No response from IP" which is misleading)
- SSH access broken (is that logged at all?)
This would make housekeeping a good bit easier without using additional scripts.

5
Discovery / Content Switches
« on: June 27, 2013, 03:22:51 PM »
Anybody using NeDi for the discovery of content switches? I would be curious if you can get the nodes from an F5.

6
News / Re: NeDi 1.0.9 Progress
« on: June 04, 2013, 11:50:16 AM »
I'm interested in by port channel informations !
You mean how to get Port-Channel information in NeDi? Just send me a short private notice and I will send the source code.

7
News / Re: NeDi 1.0.9 Progress
« on: June 03, 2013, 09:33:26 AM »
Hi Remo,

great to see, there is already development in the project again. Here are some ideas from my side. Maybe you like some of them ;-)
  • functionality to add the server into an ACL based on the user in a config file and the ACL delivered in a parameter (I use a separate script at the moment and try to get in into nedi)
  • option to turn on auto-deletion of devices if not re-discovered within x days (I use an SQL script at the moment that deletes devices that have not been discovered within the last week)
  • option to turn on auto-deletion for events older than x days (again I currently use an SQL)
  • storing the used config in NeDi within the discovery (implemented in my system as enhancement) -> allows reports and assures correct user for Devices-Write
  • Devices-Write with logging functionality (currently replaced Devices-Write by an individual solution)
  • Devices-Write with parameters (being able to use the output for some other commands)
  • vendor MAC table in NeDi to join SQLs to this table for vendor MACs (I currently use a single table)
  • port-channel information (I currently do have this based on SSH commands)

If you want to have details on some of my implementations, just let me know.

Best regards,
Matthias

8
News / Re: NeDi 1.0.8 Progress
« on: November 27, 2012, 03:15:32 PM »
How about an autodelete process for monitoring?

e.g. if the device is down > 10 days then delete?
Just make a cron job with an SQL.
mysql <database>--batch --user=<user> --password=<password> < <sql_file>

in the sql file:
delete from monitoring where <condition>;

9
News / Re: NeDi 1.0.8 Progress
« on: November 19, 2012, 09:05:52 AM »
@raider, you mean Aruba (the others should have links)? LLDP support is on their roadmap AFAIK. However I plan to bring back MAC based links to a certain extent. That could address this...
Both. Cisco APs have Links and appear as a Node (at least in the discovery; NeDi then ignores them if set via nosnmpdev). The question is:
Will there be 2 entries in the link table per AP? 1 to the Controller, 1 to the Switch?

10
News / Re: NeDi 1.0.8 Progress
« on: November 16, 2012, 09:01:14 AM »
Remo,
a question. Will there be two link types for APs in the future? If not, will the link be between the controller and the AP or between the actual switch and the AP?
Sorry, can't test myself at the moment ...
Thanks,
raider82

11
Discovery / Missing values in fields
« on: November 14, 2012, 01:32:41 PM »
Hi all,

just wanted to share some information with you, in case you have a similar issue.

I had one seedlist with about 400 devices. 250 were lacking information like the serial and bootimage. Within Defgen, I could request those fields and the requested values were correct. There were even events, telling me the serial was changed from '-' to the correct one. But still, I was missing those in the database.

The root cause? nosnmpdev contained to pipes after each other (e.g. 'Phone||Controller'). So what happened ist that NeDi accepted any device as a neighbor that needs to be written to the device list. First, devices were discovered correctly and then their values were deleted again, as the result of a neighbor entry.

Troubleshooting in this case is a bit tricky. The devices showed green lights next to SNMP, as mentioned, Defgen showed the correct values, etc. The values stayed in the database when additionally discovered with the -a flag. On the next day, they disappeared again. There was an event, saying it replaced '-' with the correct serial or bootimage, but no event, that said it replaced it again! The only thing, that caused my attention was that I found three values for "WDEV" when I logged the whole discovery and grepped for the device. That gave me the relevant hint.

Maybe this piece of information is useful for somebody.

12
Discovery / Re: Nexus & libcli
« on: October 26, 2012, 01:02:54 PM »
Found an open topic (I think it is one).
Currently I don't see nodes on Nexus Devices.

All following changes refer to "sub BridgeFwd" in libcli.

I think, I found the reason for this.
1st of all, Nexus was not part of the checking:
Changed
if($main::dev{$na}{os} =~ /^IOS/){
to
if($main::dev{$na}{os} =~ /^(IOS|NXOS)/){

Then the interface name was missing -> changed
 if ($col =~ /^(Te|Gi|Fa|Do|Po|Vi)/){$po = &misc::Shif($col)}
to
 if ($col =~ /^(Te|Gi|Fa|Do|Po|Vi|Eth[0-9])/){$po = &misc::Shif($col)}

Then I was stuck, since Nedi knows the interfaces as Et..., but they come in as Eth... with "sh mac address-table dynamic" -> I was stuck at this line:
if(exists($misc::portprop{$na}{$po}) ){                                         # IF exists?
fixed with change to
if(exists($misc::portprop{$na}{$po}) || exists($misc::portprop{$na}{substr($po,0,2) . substr($po,3)}) ){

This still does not fix the port-channels which are shown e.g. as "port-channel1" in NeDi, but are expected as Po1 (I guess).

Remo, can you help me out here? I am not quite sure, all my changes are correct in the overall context and I would be supposed to solve the port-channel topic the same way. Nodes on the Eth-Interfaces however do now appear correctly in NeDi.

13
Discovery / Re: Nexus & libcli
« on: October 24, 2012, 08:59:54 AM »
Short update:
"sh cam dyn" does not work of course. Just use "sh mac-address table dynamic" as usual.

14
News / Re: NeDi 1.0.8 Progress
« on: September 07, 2012, 02:13:00 PM »
Ok, as promised: http://www.nedi.ch/pub/nedi-250.tgz
Thanks Remo. It's great to see NeDi is developing in such a good direction.
Just installed it on a test box and it looks good at first glance.

Attached is a backport of the new node functionality for 1.0.7. It might be useful for people with large networks and several threads for discovery. Just replace sub WriteNod with the attachment. Note: don't take WriteNod from 1.0.8, since the database structure is different (e.g. IPv6). This is the same functionality - only the new database fields of 1.0.8 were removed.

15
Installation / Re: Installing NeDi on Mountain Lion
« on: September 05, 2012, 07:57:30 AM »
Have you thought about a virtual machine? You should be able to get (almost) any dependencies fixed with Ubuntu and a package manager. This will also include automatic updates. VirtualBox should be fine - so the whole solution would be free of costs.

If you install NeDi within OS X, I assume, you need to fix a lot of dependencies on your own and work on the try and error principle. Maybe something like MacPorts can help for PHP, Perl, MySQL, their modules, dependencies and updates?

Sorry - no installation instruction. But I hope it still might help.

Pages: [1] 2 3 ... 7