added exinda mibs and updated fortinet

[inphobia]

first try at getting exinda mibs known

[inphobia]

added exinda mibs, updated fortinet (but it seems fortinet merged the analyzer & manager diffs in 1 file)

[inphobia]

upon closer inspection, while this is the latest version released by fortinet of fortinet-fortigate-mib.mib, several fortigate models have gone missing.

for example:
fgt60ADSL OBJECT IDENTIFIER ::= { fgModel 602 }

is no longer present in the version. perhaps the product is end of life, but what are the guidelines when items get removed from an official mib?

[JeroenvIS]

but what are the guidelines when items get removed from an official mib?

I'm not sure whether we have "official" guidelines on that, but my rule of thumb is:

• Keep as many uniqe translations as possible
• Try to maintain a MIB set that is better than the official vendor release
• Don't remove obsolete translations

eg in the HP/ProCurve product range, I also try to keep objects for products that showed up in the MIB at some point, but haven't actually been released. Downside is that it makes MIB maintenance more difficult though.

[inphobia]

i've been thinking about this for a while but it seems a maintenance problem that will be only be getting bigger as time goes on. perhaps the mailinglist is a better place to take this discussion, but i'll alrdy write it down here for further reference.

to me it seems like an interesting idea to have the vendor provided mibs as is in netdisco, to making updating straightforward, but provide some kind patch/diff file with models and/or other items that the vendor has removed but we wish to keep in.

this could:

• make updating mibs more of copy & replace file process that's the same for all vendors.
• make it clear what local changes are to the mibs
• make it clear there are indeed local changes made to the mibs so they are less likely to get missed in further updates.

there is alrdy quite a bit of this infrastructure in place, since the mib update process (https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs) compares contents in steps 10 -> 12. perhaps removals can be caught here and kept track for the changes/additions/removals we like to keep compared to the current vendor mibs?

i'll see what i'll do with this pull request, since the fortinet part is clearly botched due to removals. the exinda part ( 51c5a4a ) however seems fine to me & will be needed for for the snmp::info exinda module i'm almost done with.

[inphobia]

finally figuring out how git works, so made a clean branch with just the exinda changes. will close this pull request. fortinet updates are still in the pipeline but need more work.

clean pull request in #60