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

Pages: [1]
1
Discovery / Discovery notification problem - is MAC changed type to MAC
« on: November 27, 2017, 11:34:49 PM »
I am seeing some odd interface changes from discovery. Looking at my logs I see things like:

Code: [Select]
25519 Warning 27.Nov 17 22:50 xxxx Connection Change (lnc), Devices-Status em1 is MAC changed type to MAC
25512 Warning 27.Nov 17 22:45 xxxx Connection Change (lnc), Devices-Status em1 was MAC changed type from MAC
25415 Warning 27.Nov 17 21:30 xxxx Connection Change (lnc), Devices-Status em1 is MAC changed type to MAC
25408 Warning 27.Nov 17 21:25 xxxx Connection Change (lnc), Devices-Status em1 was MAC changed type from MAC

The device in question is a pfSense firewall running 2.4.2 and LADVD 1.2.2. My nedi system is running 1.6.100.

Any ideas why the interface type would be seen as changing to the same type?

2
Discovery / JunOS cli and collecting configs
« on: November 17, 2017, 12:25:37 AM »
I have a Juniper EX2200 running JUNOS 12.3R9.4. This device is "special", as rather than an enable prompt you get dumped in a unix-like shell on login and have to use the "cli" command to get to the configuration interface. I have hacked support for it into libcli.pm, but this will break any other Juniper devices that use enable (like sane devices do).

Is there a better way to handle this? It still reports as JunOS, so I don't see a way to make this a cleaner patch.
Code: [Select]
diff -rub inc/libcli.pm.orig   inc/libcli.pm
--- inc/libcli.pm.orig 2017-11-16 15:21:29.155861226 -0800
+++ inc/libcli.pm 2017-11-16 15:12:37.612511327 -0800
@@ -433,9 +433,11 @@
 $cmd{'FujitsuE10CB'}{'page'} = 'terminal pager disable';

 # JUNIPER
-$cmd{'JunOS'}{'ropr'} = 'GitsDoNid';
+#$cmd{'JunOS'}{'ropr'} = 'GitsDoNid';
+$cmd{'JunOS'}{'ropr'} = '[\w+().-]+%\s?$';;
 $cmd{'JunOS'}{'enpr'} = '[\w+().-]+>\s?$';
-$cmd{'JunOS'}{'enab'} = 'enable';
+#$cmd{'JunOS'}{'enab'} = 'enable';
+$cmd{'JunOS'}{'enab'} = 'cli';
 $cmd{'JunOS'}{'shcf'} = 'show configuration | no-more';
 #$cmd{'JunOS'}{'dfwd'} = 'show ethernet-switching table | no-more'; # Sneuser: for switches only
 $cmd{'JunOS'}{'cfst'} = '^## Last commit';

3
Definition Files / New OUI icons
« on: September 09, 2013, 12:29:28 AM »
It's not quite a new def file, but I've added a flock of new OUI icons. I didn't like seeing all of the '?' icons, so I grabbed a handful of vendor logos and cut them down.

Is there a better place to post a patch and the new icons than here?

Code: [Select]

--- html/inc/libnod.php.orig 2013-09-07 23:15:24.000000000 -0700
+++ html/inc/libnod.php 2013-09-08 15:21:49.000000000 -0700
@@ -15,6 +15,7 @@
  elseif (stristr($m,"Acrosser")) {return  "acs";}
  elseif (stristr($m,"ACTIONTEC")) {return  "atec";}
  elseif (stristr($m,"ADAPTEC")) {return  "adt";}
+ elseif (stristr($m,"Adder")) {return  "addr";}
  elseif (stristr($m,"ADVANCED DIGITAL INFORMATION")) {return  "adi";}
  elseif (stristr($m,"ADVANCED TECHNOLOGY &")) {return  "adtx";}
  elseif (stristr($m,"ADVANTECH")) {return  "adv";}
@@ -37,6 +38,7 @@
  elseif (stristr($m,"B. R. Electronics")) {return  "bre";}
  elseif (stristr($m,"BECKHOFF")) {return  "bek";}
  elseif (stristr($m,"Billion")) {return  "bil";}
+ elseif (stristr($m,"B-Link")) {return  "bli";}
  elseif (stristr($m,"BROADCOM")) {return  "bcm";}
  elseif (stristr($m,"BROCADE")) {return  "brc";}
  elseif (stristr($m,"BROTHER INDUSTRIES")) {return  "bro";}
@@ -51,6 +53,7 @@
  elseif (stristr($m,"COMPAQ")) {return  "q";}
  elseif (stristr($m,"Comtech")) {return  "cth";}
  elseif (stristr($m,"CRAY")) {return  "cra";}
+ elseif (stristr($m,"Data Robotics")) {return  "dro";}
  elseif (stristr($m,"D-LINK")) {return  "dli";}
  elseif (stristr($m,"DELL")) {return  "de";}
  elseif (stristr($m,"DIGITAL EQUIPMENT")) {return  "dec";}
@@ -84,6 +87,7 @@
  elseif (stristr($m,"GKB")) {return "gkb";}
  elseif (stristr($m,"Go Networks")) {return "gns";}
  elseif (stristr($m,"GOLDSTAR")) {return "gs";}
+ elseif (stristr($m,"Hi-flying")) {return  "hif";}
  elseif (stristr($m,"High Tech Computer")) {return  "htc";}
  elseif (stristr($m,"Hon Hai Precision")) {return  "amb";}
  elseif (stristr($m,"HTC")) {return "hcc";}
@@ -132,6 +136,7 @@
  elseif (stristr($m,"Newisys")) {return "nws";}
  elseif (stristr($m,"Nexcom")) {return "nxm";}
  elseif (stristr($m,"NEXT")) {return  "nxt";}
+ elseif (stristr($m,"Nintendo")) {return  "nin";}
  elseif (stristr($m,"NOKIA")) {return  "nok";}
  elseif (stristr($m,"NUCLEAR")) {return  "atom";}
  elseif (stristr($m,"Oracle")) {return "ora";}
@@ -139,6 +144,7 @@
  elseif (stristr($m,"PATTON")) {return "pat";}
  elseif (stristr($m,"PAUL SCHERRER")) {return  "psi";}
  elseif (stristr($m,"PayTec AG")) {return  "pay";}
+ elseif (stristr($m,"PC Partner")) {return "pcpa";}
  elseif (stristr($m,"PC-PoS")) {return "pcp";}
  elseif (stristr($m,"PEGATRON")) {return "peg";}
  elseif (stristr($m,"Peplink")) {return "pep";}
@@ -157,6 +163,7 @@
  elseif (stristr($m,"RICOH")) {return  "rco";}
  elseif (stristr($m,"Riverbed")) {return "riv";}
  elseif (stristr($m,"Rockwell")) {return "ra";}
+ elseif (stristr($m,"ROSEMOUNT CONTROLS")) {return  "epm";}
  elseif (stristr($m,"Routerboard.com")) {return "rbd";}
  elseif (stristr($m,"RUBY TECH")) {return  "rub";}
  elseif (stristr($m,"SAMSUNG")) {return "sam";}
@@ -165,6 +172,7 @@
  elseif (stristr($m,"SERCOM")) {return  "ser";}
  elseif (stristr($m,"SHIVA")) {return  "sva";}
  elseif (stristr($m,"SHUTTLE")) {return  "shu";}
+ elseif (stristr($m,"Slim")) {return  "slim";}
  elseif (stristr($m,"SIAE")) {return "sia";}
  elseif (stristr($m,"SIEMENS")) {return  "si";}
  elseif (stristr($m,"SILICON GRAPHICS")) {return  "sgi";}
@@ -180,6 +188,7 @@
  elseif (stristr($m,"TECO INFORMATION ")) {return  "tec";}
  elseif (stristr($m,"TEKTRONIX")) {return  "tek";}
  elseif (stristr($m,"Tilgin")) {return "til";}
+ elseif (stristr($m,"TiVo")) {return  "tiv";}
         elseif (stristr($m,"TOKYO"))                            {return  "tok";}
  elseif (stristr($m,"TOSHIBA")) {return  "tsa";}
  elseif (stristr($m,"TP-LINK")) {return "tpl";}
@@ -187,12 +196,14 @@
  elseif (stristr($m,"TYAN")) {return  "tya";}
  elseif (stristr($m,"U.S. Robotics")) {return  "usr";}
  elseif (stristr($m,"Ubiquiti")) {return "ubi";}
+ elseif (stristr($m,"Universal Devices Inc.")) {return  "udi";}
  elseif (stristr($m,"Universal Global Scientific")) {return "ugs";}
  elseif (stristr($m,"USC CORPORATION")) {return  "usc";}
  elseif (stristr($m,"USI")) {return  "usi";}
  elseif (stristr($m,"UTSTARCOM")) {return "uts";}
  elseif (stristr($m,"Vanguard")) {return "vgd";}
  elseif (stristr($m,"VIA TECHNOLOGIES")) {return  "via";}
+ elseif (stristr($m,"VIA NETWORKING TECHNOLOGIES")) {return  "via";}
  elseif (stristr($m,"Vivotek")) {return "viv";}
  elseif (stristr($m,"VMWARE")) {return  "vm";}
  elseif (stristr($m,"WESTERN")) {return  "wdc";}

4
Discovery / SNMP errors with multiple community strings
« on: January 19, 2011, 06:39:11 PM »
I am getting complaints from our network team that NeDi is causing SNMP errors on our devices.  From what I can tell, it's because we have multiple communities defined in our nedi.conf file.  For example, I have:
Code: [Select]
comm            mycommstring
comm            public
The first is the community string in use on most of our network devices, the second is for non-network devices and a handful of older devices.

Our monitoring system is generating messages like:
Quote
Alarm Relation Report
Device neworkswich(192.168.##.##) receives an SNMP message with an erroneous community string

I'm assuming this is because it is NeDi is querying the device with the "public" community string even though it has already successfully used "mycommstring".  Is there a way to have it not query with a second string if the first is successful and/or make NeDi use the stings in the order they are in the file?

Thanks!

Pages: [1]