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

Pages: [1]
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




2
Discovery / Re: juniper not discovered, polled
« on: December 29, 2017, 04:43:47 PM »
Changing the lldp protocol setting on the juniper was KEY, but so was adjusting the discover setting to go along with the Juniper change.

Using the juniper configuration

 "set protocols lldp management-address <IP>"

 in conjunction with defgen discover "LLD" ("plain vanilla") has allowed me to remove all the juniper management IPs from the NeDi seedfile.

  Thanks again for the help, and Happy New Year!

3
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.

4
Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: August 11, 2017, 08:22:36 PM »
Oh, actually my colleage John did some serious MIB diving this week and now has port vlan index working.  Theres a change needed for vlan names, (the vlan index is appended with a "+") but that'll come. so for now: (i suspect these are the relevant entries in the .def.  we got 95% of the way there using the 4200 as basis for 4300)

VLnams  1.3.6.1.2.1.17.7.1.4.3.1.1
VLnamx
IFvlan  1.3.6.1.2.1.17.7.1.4.5.1.1
IFvlix  1.3.6.1.2.1.17.1.4.1.2

// sample

Vlan   Name
615   N-10.248.121.0-24+615   
616   N-10.248.122.0-24+616
// for some reason via this oid, the vlid tacked on after "+" (above) !  we have another oid to try asap.

                            IF Name     Alias     Port Vlan Index 
Ethernet - Link up/Admin up   ge-1/0/39         139
Ethernet - Link down/Admin up   ge-1/0/33   EMCS   114
Ethernet - Link down/Admin up   ge-1/0/40         139
Ethernet - Link down/Admin up   ge-1/0/42         32
Ethernet - Link up/Admin up   ge-1/0/44         3124
Ethernet - Link up/Admin up   ge-1/0/46   0463-101   615
Ethernet - Link down/Admin up   ge-1/0/45         32
Ethernet - Link up/Admin up   ge-1/0/47   0463-102   615

John will share the full defgen file, that we've concoted with your help, when he's satisfied he has it where he wants it.


5
Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: August 11, 2017, 02:59:18 PM »
thanks for this tip; We'll try leveraging it!

6
Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: August 01, 2017, 06:59:21 PM »
So does anyone have an idea why putting this OID into the PVID field defgen: 1.3.6.1.2.1.17.7.1.4.5.1.1 and "running it" shows the list of port vlans in the popup window (output) yet . . .  port vlan index still won't show in discover?

# Definition for 1.3.6.1.4.1.2636.1.1.1.2.63 created by Defgen 2.0 on 1.Aug 2017 (healy@bnl.gov)
 
# Main
SNMPv   2HC
Type   Ex4300-BNL
Typoid   
Sysdes   
OS   JunOS
Icon   w3an
Size   1
Bridge   qbriX
ArpND   old
Dispro   LLDP
Serial   1.3.6.1.4.1.2636.3.1.3.0
Bimage   1.3.6.1.2.1.54.1.1.1.1.4.2
CfgChg   
CfgWrt   
VLnams   1.3.6.1.2.1.17.7.1.4.3.1.1
VLnamx   1.3.6.1.4.1.2636.3.40.1.5.1.5.1.5
Group   
Mode   
 
# Interfaces
StartX   
EndX   
IFname   1.3.6.1.2.1.31.1.1.1.1
IFaddr   old   
IFalia   1.3.6.1.2.1.31.1.1.1.18
IFalix   
InBcast   1.3.6.1.2.1.31.1.1.1.3
InDisc   1.3.6.1.2.1.2.2.1.13
OutDisc   1.3.6.1.2.1.2.2.1.19
IFvlan   1.3.6.1.2.1.17.7.1.4.5.1.1
IFvlix   1.3.6.1.2.1.17.7.1.4.5.1.1
IFpowr      
IFpwix   
IFdupl   
IFduix   
Halfdp   
Fulldp   
 
# Modules
Modesc   1.3.6.1.4.1.2636.3.1.8.1.6.7
Moclas   
Movalu   
Moslot   1.3.6.1.4.1.2636.3.1.8.1.2.7
Mostat   
Mostok   
Modhw   1.3.6.1.4.1.2636.3.1.8.1.10.7
Modsw   
Modfw   1.3.6.1.4.1.2636.3.1.8.1.8.7
Modser   1.3.6.1.4.1.2636.3.1.8.1.7.7
Momodl   1.3.6.1.4.1.2636.3.1.8.1.13.7
Modloc   
 
# RRD Graphing
CPUutl   1.3.6.1.4.1.2636.3.1.13.1.8.7.1.0.0   
Temp   1.3.6.1.4.1.2636.3.1.13.1.7.7.1.0.0   
MemCPU   1.3.6.1.4.1.2636.3.1.16.0   -%
Custom   Buffer;G;%   1.3.6.1.4.1.2636.3.1.13.1.11.7.1.0.0


7
Definition Files / Re: Wanted - Juniper ex4300 definition file
« on: July 19, 2017, 09:29:22 PM »
This is a step in the right direction for sure, and i think much more interface info is present now,  thanks very much.  The "IF Name" is at least now "ge-0/*" instead of the snmp ifIndex NUMBER.  Sadly,  still doesn't bring up the port vlan index; they're all still "0" (zero)  so i guess 1.3.6.1.4.1.2636.3.40.1.5.1.5.1.5 isn't "it".  will dig at that next.

// this looks very much like the port vlan index, seems to match our config

$ snmpwalk -c xxxx -v 2c 10.248.120.105 1.3.6.1.2.1.17.7.1.4.5
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.490 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.491 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.492 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.493 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.494 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.495 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.496 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.497 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.498 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.499 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.500 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.501 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.502 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.503 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.504 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.505 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.506 = Gauge32: 27
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.507 = Gauge32: 252
SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.508 = Gauge32: 27

not getting to far trying to use 1.3.6.1.2.1.17.7.1.4.5.1.1, but i'll keep at it (and accept any help! :)

8
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!

9
Discovery / Re: devices stop updating after 'Discover Replaced'
« on: February 01, 2017, 10:32:36 PM »
The fix:  adding "LLDP" to the discovery protocol setting in defGen for the head-end switches.  Normal periodic discovery now updates all the existing dowstream devices in question.

 Thanks to all who contributed to the solution.

bobh

10
Discovery / Re: devices stop updating after 'Discover Replaced'
« on: January 31, 2017, 04:22:46 PM »
and i'm trying to NOT delete devices, if possible (i know its not always possible)

11
Discovery / Re: devices stop updating after 'Discover Replaced'
« on: January 31, 2017, 04:22:09 PM »
yes, we're using -p: (from the cron:)   " /var/nedi/nedi.pl -p "

12
Discovery / Re: devices stop updating after 'Discover Replaced'
« on: January 30, 2017, 03:53:46 PM »
No, None of the devices in this group show up as any other hosts, not with same IP, same serial# nor with same name.

13
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]