Malformed LWAPP MIB

[bastischubert]

Hey there, 👋

while working on the https://github.com/prometheus/snmp_exporter i found the following errors in the mib definitions. see this PR the proposed fixes.

https://github.com/cisco/cisco-mibs/pull/178

Also notable: The contact details in the MIB files reference "cs-wnbu-snmp@cisco.com" which does not exist anymore. You might want to update this as well. This adress is used in various MIB files - fyi.

[Mark Elsen]

  - @bastischubert      Cisco  will no longer engage on that ; these days snmp is getting outdated
                                  as overall management platforms such as Catalyst Center, Meraki Dashboard , 
                                  others , migrate to API's  for polling or setting variables

  M.

[Rich R]

@Mark Elsen is right - Cisco is not actively maintaining the SNMP MIBs - they're effectively End of Software Maintenance.

All effort today goes into the YANG APIs and streaming telemetry.

In any case - if you want engagement on any issue you find, it can only be done by opening a TAC case with Cisco TAC support under a contract.  If TAC can reproduce the issue then they open a bug for it which gets assigned to the software development teams for resolution (or not if they decide it is too low priority or no longer supported).

[bastischubert]

Is any of you affiliated in any way with cisco? their contribution guides clearly state to EITHER contact TAC OR support forums (https://github.com/cisco/cisco-mibs/blob/main/CONTRIBUTING.md) 

Since i do not have a support contract, i can't open a case with the TAC and tbh there is NO viable way for an OSS project to reach out to Cisco and tell them whats wrong on their side.

[Rich R]

> Is any of you affiliated in any way with cisco?
No.  There are a few Cisco TAC people who dip into the community occasionally but it's on a voluntary/informal basis and there's no guarantee they could take anything to the respective business unit. They will usually recommend opening a TAC case as that is the only formal path to engage with support.

The file you linked above https://github.com/cisco/cisco-mibs/blob/main/CONTRIBUTING.md pretty much says exactly that!
🪲 Issues

• Issues with MIB files MUST be raised with Cisco Technical Assistance Center (TAC) so a Cisco Defect can be created and Cisco Developer can be assigned.
  • This includes syntax issues, missing values, missing imports or other general problems with the files.

So yes, we can help with general stuff, but we cannot fix a broken Cisco MIB - that can only be done via TAC.