|Think about Loose Coupling|
The general idea: SNMP v1 has set, get, get_next. set($oid,$value); ($oid, $value) = get($oid); ($oid, $value) = get_next($root). For the set, get you a full OID leaf value, for the get_next you can use either any OID value because get_next returns the next available OID in the MIB after the one you gave it. So if you have a tree like:
18.104.22.168.0 = 42 22.214.171.124.1 = 43 126.96.36.199.3 = 44 188.8.131.52.0 = 'a' 184.108.40.206.1 = 'b' 220.127.116.11.3 = 'c' get(18.104.22.168) -> error get_next(22.214.171.124) -> (126.96.36.199.0, 42) get_next(188.8.131.52.0) -> (184.108.40.206.1, 43) ... get_next(220.127.116.11.3) -> 18.104.22.168.0, 'a) ... get_next(22.214.171.124.3) -> 126.96.36.199.something, something)
A walk just does a get_next over and over until the returned OID is outside of the tree root you gave it to start with. In this case if you started with 188.8.131.52 it would stop at 184.108.40.206.3 and not give you 220.127.116.11 and later.
A get_table is just a wrapper that walks multiple tree roots at the same time, e.g. get_table(18.104.22.168, 22.214.171.124) would return all six of the above values.
SNMP v2c and v3 have the bulk versions of these, they can just request/get multiple OIDs in the same data packet rather than doing a get_next for each OID in turn.
IIRC, the Net::SNMP module returns everything in a hash reference. The SNMP module for the net-snmp library returns VarBind objects (array references) and will return a get_table in columns like:
[ [ 126.96.36.199.0, 42, 188.8.131.52.0, 'a' ], [ 184.108.40.206.1, 43, 220.127.116.11.1, 'b' ], ]
This is by no means a detailed description, method names, signatures, returns, details differ depending on which SNMP module you're using, and which version of SNMP you're using to communicate with the device. But it all pretty much breaks down to set, get, get_next.