[c-nsp] SFP DOM SNMP Polling?

[Tony Tauber]

I'm no expert in EEPROMs but recall awhile back we had an optical vendor
(transport-side, not router-side) that did do frequent writes (maybe it was
for performance info) to EEPROM and burned them out that way after a couple
of years.  Maybe your vendor is saying they don't support reporting this
way because they would do it via writing to the EEPROM which is bad for
it.  Not saying whether they could do it some different way that would make
it supportable, but who knows.  May be some fundamental
shortcoming/limitation of their design (or their OEM's design).

$0.02
Tony

On Tue, Nov 22, 2016 at 12:11 PM, Michael Loftis <mloftis at wgops.com> wrote:

> On Tue, Nov 22, 2016 at 6:32 AM, Tim Durack <tdurack at gmail.com> wrote:
> > I have a vendor that does not support SFP DOM SNMP polling. They state
> this
> > is due to EEPROM read life cycle. Constant reads will damage the SFP.
>
> Complete and total garbage.  Reading from EEPROM and Flash both DO NOT
> WEAR.  It is the erase+write cycle that wears them.  Further typical
> EEPROM life cycle is ~1M erase/write cycles.  If you wrote it every
> minute you could conceivably wear it out in a couple years...but thats
> flat out not how it works.  The EEPROM, if any, is not going to be
> used for statistics data....maybe fail counts of some kind, lifetime
> (hours) maybe...that sort of thing.
>
>
> >
> > We SNMP poll SFP DOM from Cisco equipment without issue.
> >
> > Not heard this one before. Trying to see if there is some validity to the
> > statement. Thoughts?
> >
> > Tim:>
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>
> --
>
> "Genius might be described as a supreme capacity for getting its possessors
> into trouble of all kinds."
> -- Samuel Butler
>