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 - healy@bnl.gov

Pages: [1]
Discovery / Normal Poll fails, but Inventory Poll is successful
« on: January 02, 2018, 11:09:52 PM »
 The reason for this post:  for some ODD reason, the inventory run (second crontab below) is successful for several devices that, for some reason, FAIL TO UPDATE during the normal 2-hr cycle (first crontab below).  Obviously, the arguments are VERY different, but still - this makes no sense to me.  So i'm wondering if anyone has seen this or can tell me the cause based on the arguments I used in the two crontab entries.  Device status shows "Discovery Outdated" and "last" is: 1:11 1-Jan-18 (as per inventory cron).  The host name, mac or IP of at least one of these does NOT show up in the logfile nedi.lastrun at all after the run is complete, much less with any error.

Here is my crontab entry for our normal every-two-hours polling of the network:

  #-  Almost every 2 hrs (not 24)
  0 2,4,6,8,10,12,14,16,18,20,22 * * * /var/nedi/nedi.pl -p > /var/nedi/log/nedi.lastrun 2>&1

The "inventory run" crontab is given below.
#-  run inventory poll at 1.11am on Monday morning ea week
11 1 * * 1 /var/nedi/nedi.pl -Aall -SAFGgadobewituvjp -Yam > /var/nedi/log/nedi_Y.lastrun 2>&1

Discovery / juniper not discovered, polled
« on: November 16, 2017, 04:09:12 PM »
Despite using LLDP, and seeing the juniper neighbors in both a cisco and juniper "upstream device" i CAN NOT GET any junipers to discover or update UNLESS i put their IP addresses in the seed file. Their managment subnet is already in the seedfile, but thats not enough.  I don't like having to manually add every new juniper to the seedfile; such manual intervention risks errors, missing a device, typing wrong ip etc.  discovery does look good (as well it should!)

Although ciscos have not met our expecttions as a campus lan switching fabric (hence juniper rollout) NeDi DID discover them w/out my intervention.  I'm betting theres a way, and i'm just missing something.  (wouldn't be the first time!)   We have mostly EX4300s (24,48,32f) currently on 16.1R5.7 with a handful of ex2300 in some version of 15; don't worry abt those right now!

Pls assist if you have any experience w/Juniper discovery in NeDi.

Definition Files / Wanted - Juniper ex4300 definition file
« on: July 11, 2017, 09:39:42 PM »
Can someone please! share a working Juniper DEFINITION file - Especially, one that includes the port VLAN index in the interfaces list? I currently see all 0s for pvid.    If it's already in the forum. i apologize, but my search didn't find it.

We currently have just two models;   ex4300-32f & ex4300-48p - both running Junos: 16.1R3.10

 We'll be adding ex2300s later, but i'll cross that bridge...   I'm praying that i'm not the first one to deal with this.

Thanks in advance for any help!

Discovery / devices stop updating after 'Discover Replaced'
« on: January 26, 2017, 02:52:23 PM »
When an upstream switch was replaced, all downstream devices stopped updating after numerous discovery/polling cycles.
the switches in question were not altered in any way.
using the "discover now" button in the device status snmp field will successfully poll the device. HOwever, after the next polling cycle the device will still not update.  how can "Discover Replaced" status be "cleared" or how can normal discover be re-established?

Pages: [1]