Welcome, Guest. Please login or register.

Author Topic: HP Procurve E3500YL-48G-PoE def  (Read 3028 times)

atpoirie

  • Guest
HP Procurve E3500YL-48G-PoE def
« on: April 13, 2012, 03:22:25 PM »
Had to change file extension to txt to upload.  Change back to .def to use.
« Last Edit: April 13, 2012, 05:02:33 PM by atpoirie »

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: HP Procurve E3500YL-48G-PoE def
« Reply #1 on: April 16, 2012, 06:31:30 PM »
Excellent, thanks  ;D

You can zip the files and just upload the archive (or mail it to me). Renaming on OSX is a bitch!

Can you check whether this line works on this model?

Temp   1.3.6.1.2.1.99.1.1.1.4.5001
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

atpoirie

  • Guest
Re: HP Procurve E3500YL-48G-PoE def
« Reply #2 on: April 16, 2012, 07:40:57 PM »
I'll make sure and do zip from now on.  It would be nice to just be able to upload .def filetype, not sure how much control you have over that.

The Temp 1.3.6.1.2.1.99.1.1.1.4.5001 returned no such instance.  The E3500 is essentially the non-modular E5400 series so Temp is at 1.3.6.1.2.1.99.1.1.1.4.11

atpoirie

  • Guest
Re: HP Procurve E3500YL-48G-PoE def
« Reply #3 on: April 16, 2012, 08:41:25 PM »
Updated - I've zipped def's for all the E3500 series switches I have.  They now include Temp as well

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2780
    • View Profile
    • NeDi
Re: HP Procurve E3500YL-48G-PoE def
« Reply #4 on: April 16, 2012, 09:32:15 PM »
Err, bummer I ment to paste that one  :-[ The 5001 is the OID from the 3800...
« Last Edit: April 16, 2012, 10:14:55 PM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

atpoirie

  • Guest
Re: HP Procurve E3500YL-48G-PoE def
« Reply #5 on: April 16, 2012, 09:34:17 PM »
The OID's make for a lot of numbers to keep straight, I'm constantly afraid that I've typed something incorrectly.  Either way, got me to go back and double check my def files.  ;)