Hi, Henrique.
Both of the repositories from SLAC are forks for the code from NSCL/FRIB. One originated from Git the other one from a tar.gz downloaded from
https://groups.nscl.msu.edu/controls.
We have two because two separate teams started these repositories independently. Usually, we just make small modifications so the modules can be built in SLAC’s environment. I would say that the right approach
is to use the source code from NSCL/FRIB which is the one we use, too.
Cheers,
Márcio
From:
Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Priller, John via Tech-talk <tech-talk at aps.anl.gov>
Date: Friday, July 26, 2024 at 06:50
To: Henrique F. Simoes <henrique.simoes at lnls.br>, tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Difference among SNMP support modules for general SNMP-aware devices
BEWARE: This email originated outside of our organization. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe.
Hi;
I'm the maintainer of the NSCL/FRIB version of SNMP support. I see you've already found our website and documentation (your [5]). The github location hasn't been updated in some time, the person
we had semi-officially maintaining that content left our lab some time back.
I'm happy to help with any questions you might have. We use the package to communicate with ISEG power supply crates, and remote power-distribution units (providing power on/off switching for things
like cameras that sometimes hang up due to magnetic fields or neutrons or etc in our accelerator).
- John Priller
From: Henrique F. Simoes <henrique.simoes at lnls.br>
Sent: Friday, July 26, 2024 9:08 AM
To: tech-talk at aps.anl.gov
Cc: Guilherme Rodrigues de Lima; Priller, John; mls at aps.anl.gov; paul.nord at valpo.edu; nick.rees at diamond.ac.uk; florian at ep1.ruhr-uni-bochum.de; eric at norum.ca; bhill at slac.stanford.edu; marcio at slac.stanford.edu
Subject: Difference among SNMP support modules for general SNMP-aware devices
[EXTERNAL] This email originated from outside of FRIB
Hi,
We are implementing an IOC for an Aruba switch using SNMPv2. We noticed there
are two SLAC repositories providing a device support for the protocol:
- slac-epics/snmp [1]
- slac-epics/epics-snmp [2]
The former repository seems to be older and it supports more record types [3,
4] than the latter.
The latter has been created on GitHub in 2022 as a fork of a previous version
of the module provided by NSCL/FRIB [5], as far as I could understand. I could
see from NSCL/FRIB documentation that is was focused on some power supply
crates, but it should work for other devices as well.
Does anyone have experience with them and know if there is any other
significant difference among them in 2024 for general SNMP-aware devices?
Digging a little bit in the tech-talk archive, I could see an older thread [6]
asking this same question in 2013, but it seems more forks existed by then.
Most links are dead by now, and I do not know if any of them is still around.
Any recommendation on which module is probably better to base this and our
future SNMP-based IOCs is very welcome.
Best regards,
Henrique F. Simões
Control Software Group (SwC)
Brazilian Synchrotron Light Laboratory (LNLS)
Brazilian Center for Research in Energy and Materials (CNPEM)
[1]: github.com/slac-epics/snmp
[2]: github.com/slac-epics/epics-snmp
[3]: github.com/slac-epics/snmp/blob/134fbfd91ac83974730093330781cd1217017382/devSnmpApp/src/devSnmp.dbd
[4]: github.com/slac-epics/epics-snmp/blob/12a9cfa7b5b07bee17ae8ba7a74b460dd72811e6/snmpApp/src/devSnmp.dbd
[5]: groups.nscl.msu.edu/controls/files/devSnmp.html
[6]: epics.anl.gov/tech-talk/2013/msg00537.php
Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por
engano, por favor avise o remetente e apague-a imediatamente.
Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake,
please notify the sender and delete it immediately.
|
