Welcome, Guest. Please login or register.

Author Topic: Wanted - Juniper ex4300 definition file  (Read 5203 times)

healy@bnl.gov

  • Newbie
  • *
  • Posts: 15
  • Get with the SCRIPTING or get out.
    • View Profile
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!

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2893
    • View Profile
    • NeDi
Re: Wanted - Juniper ex4300 definition file
« Reply #1 on: July 14, 2017, 10:55:19 am »
There's a bunch of similar ones available (check with nedi.pl -y). I'd use this one as template:
Juniper             Ex4200                        1.3.6.1.4.1.2636.1.1.1.2.31
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

healy@bnl.gov

  • Newbie
  • *
  • Posts: 15
  • Get with the SCRIPTING or get out.
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #2 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! :)

healy@bnl.gov

  • Newbie
  • *
  • Posts: 15
  • Get with the SCRIPTING or get out.
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #3 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


rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2893
    • View Profile
    • NeDi
Re: Wanted - Juniper ex4300 definition file
« Reply #4 on: August 10, 2017, 03:47:55 pm »
IFvlix is required if the portindexes in the PVID table differ from the actual IF-indexes. It can't be the same OID as for PVIDs...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

healy@bnl.gov

  • Newbie
  • *
  • Posts: 15
  • Get with the SCRIPTING or get out.
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #5 on: August 11, 2017, 02:59:18 pm »
thanks for this tip; We'll try leveraging it!

healy@bnl.gov

  • Newbie
  • *
  • Posts: 15
  • Get with the SCRIPTING or get out.
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #6 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.


big

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #7 on: August 28, 2017, 03:52:03 pm »
attached are the defgens for a juniper  EX4300 and QFX5100
They work, but your mileage may very

SchmuFoo

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Re: Wanted - Juniper ex4300 definition file
« Reply #8 on: November 27, 2019, 10:45:35 am »
attached are the defgens for a juniper  EX4300 and QFX5100
They work, but your mileage may very

Thanks for your contribution!

I also have two Juniper EX4200 as Virtual Chassis and what is working:

VLAN Name: 1.3.6.1.2.1.17.7.1.4.3.1.1

But PVID and PVIndeX drives me nutz .-) I got values, but they are totaly non-sense:

Code: [Select]
admin@SW-BN-VC-B> show ethernet-switching interfaces ge-9/0/46.0
Interface    State  VLAN members        Tag   Tagging  Blocking
ge-9/0/46.0  up     VLAN_Management     100   untagged unblocked


Code: [Select]
snmpwalk.php: snmpwalk -v2c -cCOMMUNITY IP 1.3.6.1.2.1.17.7.1.4.5.1.1 (600000 usec * 2)
-> Shows VLAN 3  :o

Code: [Select]
IF  :  1145 ge-9/0/46     1G  -   3    0 ge-9/0/46                           0
IF  :  1163 ge-9/0/46.    1G  -   3    3 ge-9/0/46.0                         0
FWDS:d4ae52bb966b on ge-9/0/46.0 Vl3 1G-- Pop:1


BTW: Is it possible to get rid of the .0 Interfaces (See attached Photos)?

P.S.: On my EX3300-48P everything is fine, excpet the weird double interfaces listing (.0 stuff)

--

# EX3200
iso.3.6.1.4.1.2636.3.40.1.5.1.5.1.2.3: "VLAN_Management"
iso.3.6.1.4.1.2636.3.40.1.5.1.5.1.5.3: 100

# EX4200
iso.3.6.1.2.1.17.7.1.4.3.1.1.3: "VLAN_Management"
iso.3.6.1.4.1.2636.3.40.1.5.1.5.1.5.3: 100
« Last Edit: November 27, 2019, 10:52:48 am by SchmuFoo »