Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNMP place marker for sonicwall NSA 2600 #886

Open
we-sell-bags opened this issue Jan 28, 2021 · 7 comments
Open

SNMP place marker for sonicwall NSA 2600 #886

we-sell-bags opened this issue Jan 28, 2021 · 7 comments

Comments

@we-sell-bags
Copy link

The device is not being fully identified.

a private email containing confidential SNMP dump has been sent
sonicwall_2600.txt.zip

has been supplied

@g-bougard g-bougard transferred this issue from fusioninventory/sysobject.ids Jan 28, 2021
@g-bougard
Copy link
Contributor

Hi @we-sell-bags
can you try the SonicWall.pm module you'll find in the SonicWall.zip attached archive ?
Place the .pm file under the lib/FusionInventory/Agent/SNMP/MibSupport folder of the agent installation. You only need to install it on the agent which is running the netdiscovery/netinventory task.

@we-sell-bags
Copy link
Author

we-sell-bags commented Feb 2, 2021

will do... im a bit behind
Ok we can see previously it got the model wrong & could not tag the serial no.
after adding you file, it now gets the model

and finally the "serial number rule" is triggering.

sonic_ok

@g-bougard
Copy link
Contributor

Thank you for the feedback, that's nice.

@we-sell-bags
Copy link
Author

its difficult to know what is most helpful to you guys....
The debug dump does not do it full justice, since it does not show both sides of the working plugin.

@g-bougard
Copy link
Contributor

This is just difficult to debug inventory with a client/server exchange protocol between the agent and the server.
What you provided is perfect: I was able to reproduce and to find required datas to develop this device support. Then you just show the SonicWall is correctly updated by the MibSupport plugin I provided.
I think you should also have noticed you can see the firmware version on the device page.

You can know use this plugin as is, it will be included in a future release so you won't loose your inventory on an agent upgrade.

I'll keep this issue opened until the release to not forget it.

@we-sell-bags
Copy link
Author

yep... i saw the firmware as well.... :-)
as long as it gets the serial number, it all seems to sync...

There must be an easier way to do this...... to save you guys all the hassle of building each one.
some sort of "Mapping" kit where a user can associate a particular section of the MIB, with a field in the GLPI

@g-bougard
Copy link
Contributor

Thanks, we will think about it ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants