| 1 |
[1] What is SMUX? |
| 2 |
|
| 3 |
SMUX is the snmp multiplexing protocol (RFC 1227). It can be used by an |
| 4 |
snmp agent to query variables maintained by another user-level process. |
| 5 |
|
| 6 |
[2] Why is it relevant to net-snmp? |
| 7 |
|
| 8 |
The original ucd-snmp agent needed a mechanism to query statistics from |
| 9 |
GateD. GateD has traditionally supported this functionality via SMUX. |
| 10 |
Hence SMUX was implemented within the ucd-snmp framework to extract |
| 11 |
routing protocol statistics from GateD. |
| 12 |
|
| 13 |
net-snmp continues to support smux, and many applications still use it. |
| 14 |
|
| 15 |
[3] What is GateD? |
| 16 |
|
| 17 |
GateD is the 'Gateway Daemon' which implements a variety of routing |
| 18 |
protocols on a variety of platforms (OSes). This was formerly available |
| 19 |
as open source, but has since been made closed and entirely un-free. |
| 20 |
Other routing protocol daemons such a quagga (http://www.quagga.net) |
| 21 |
support SMUX. |
| 22 |
|
| 23 |
[4] Can SMUX extract statistics from other user-level processes? |
| 24 |
|
| 25 |
Yes, the current implementation allows for the registration of any MIB |
| 26 |
that might be registered by a SMUX peer. |
| 27 |
|
| 28 |
[5] How does it work? |
| 29 |
|
| 30 |
Assuming 'snmpd' is already up and running, when the SMUX peer comes up, |
| 31 |
it identifies itself with an oid identifier and string password, and |
| 32 |
registers any MIBs it would like to implement. When 'snmpd' receives |
| 33 |
queries for these MIBs, it passes these queries to the peer. |
| 34 |
|
| 35 |
[6] Who implemented SMUX for ucd-snmp? |
| 36 |
|
| 37 |
SMUX was implemented by Rohit Dube. He had oodles of help from |
| 38 |
ucd-snmp-coders (Dave, Niels, Wes, Simon, Felix, Leonti) and gated-people |
| 39 |
(Acee, Feiyi, Larry, Sue). [If I missed somebody, sorry in advance and |
| 40 |
do let me know]. Later, Nick Amato re-write the entire SMUX package so |
| 41 |
the code today is mostly his. |
| 42 |
|
| 43 |
[7] How do I find out more about SMUX? |
| 44 |
|
| 45 |
Read the RFC and the code, mainly, but only for legacy code. |
| 46 |
|
| 47 |
*New* sub-agent development should use the AgentX protocol instead, |
| 48 |
which is not only standardized (RFC 2741 + 2742), but is outright superior |
| 49 |
to smux in a number of important ways (handles SET requests reliably, |
| 50 |
able to handle overlapping registrations, aware of SNMPv3 contexts, etc.) |
| 51 |
|
| 52 |
Only build new smux support if you have to. |