newdevice: Add Calix AXOS/E5-16F Detection

[djamp42]

DO NOT DELETE THIS TEXT

Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.

• Have you followed our code guidelines?

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926

[CLAassistant]

All committers have signed the CLA.

[LibreNMS-CI]

Auto-Deploy finished, Test PR at http://6926.ci.librenms.org or https://6926.ci.librenms.org

[murrant]

Does AXOS use the same mibs as E7?

Also, this should probably be more generic like .1.3.6.1.4.1.6321.1.2.4.
And you need to add an additional snmprec file: http://docs.librenms.org/Developing/os/Test-Units/

[djamp42]

I'm trying to get the MIBs, but I believe they are different, as AXOS is the new software Calix is going to.
I'm not sure what you mean by more generic, as that OID is the same one i have.
For the snmpprec file, the sysDescr returns the model number but also includes the version number of the AXOS software installed, so i'm not sure how you handle this as E5-16F could have different versions of the AXOS software on it.

1.3.6.1.2.1.1.1.0|4|Calix, Inc E5-16F AXOS-R2.2.0
1.3.6.1.2.1.1.2.0|6|1.3.6.1.4.1.6321.1.2.4.1.4

[murrant]

I mean we match by the start of the sysObectID string, so 1.3.6.1.4.1.6321.1.2.4. will likely match every AXOS device, not just E5-16F. (I had a typo in my message earlier)

We probably need to start a new OS for AXOS if they have different MIBs. I suggest calix-axos

The snmprec data is only used for testing to make sure we don't break os detection for devices. What you have there is correct.

[djamp42]

I just checked and it uses the same mibs as the e7. It actually uses less.

[LibreNMS-CI]

Auto-Deploy finished, Test PR at http://6926.ci.librenms.org or https://6926.ci.librenms.org

[LibreNMS-CI]

Auto-Deploy finished, Test PR at http://6926.ci.librenms.org or https://6926.ci.librenms.org

[laf]

So should we do this as a new OS axos.yaml if that's what this device runs?

[murrant]

AXOS is basically the SDN (They like to call it SDA) platform for Calix. I don't think it is far off from their current E7 platform at the underpinnings.

I just checked the MIBs. CALIX-PRODUCT-MIB and CALIX-SMI are the only custom MIBs they provide. They cover both product lines.

I think it would make sense to have them separate, just in case.

[laf]

You confused me then as the email notification said no but this says yes :)

@djamp42 if you can split this off into a new os called axos that would be ace, if you don't have time let us know and one of us will sort it out.

[murrant]

@laf changed my mind and edited post.

[djamp42]

@laf I would rather you do it, just because I'm not a programmer by trade. If you need any other device info let me know.

[laf]

@djamp42 I've update this now, please test the update to make sure it does what you need.

I've removed what appears to be non-relevant discovery for models in the calix range so this is limited. If you find it's missing something that was there when it was calix then let me know.

[LibreNMS-CI]

Auto-Deploy finished, Test PR at http://6926.ci.librenms.org or https://6926.ci.librenms.org

[djamp42]

Thanks, Works fine, just added another E5 and was detected as Calix with this pull request.

[murrant]

I'm not sure this is relevant to the hardware.
@djamp42 can you snmpwalk these on your device and let us know if they are valid for the hardware?

[djamp42]

E5-16F doesn't have slots, it's a single chassis of 16 gfast ports. My understanding is the E7 will support NG-PON2 and these new cards will run AXOS. They haven't been released yet.

[murrant]

@djamp42 That seems to muddle things more... I'll do some research with my Calix contacts in a couple of days.

[scrutinizer-notifier]

The inspection completed: No new issues

[laf]

Thanks for the pull request @djamp42 :)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed.