Document fully qualifying a MIB leaf in %GLOBALS and %FUNCS
This commit is contained in:
18
Info.pm
18
Info.pm
@@ -1991,8 +1991,14 @@ $INIT = 0;
|
||||
|
||||
=item %GLOBALS
|
||||
|
||||
Contains a hash in the form ( method_name => SNMP iid name )
|
||||
These are scalar values such as name,uptime, etc.
|
||||
Contains a hash in the form ( method_name => SNMP MIB leaf name )
|
||||
These are scalar values such as name, uptime, etc.
|
||||
|
||||
To resolve MIB leaf name conflicts between private MIBs, you may prefix the
|
||||
leaf name with the MIB replacing each - (dash) and : (colon) with
|
||||
an _ (underscore). For example, ALTEON_TIGON_SWITCH_MIB__agSoftwareVersion
|
||||
would be used as the hash value instead of the net-snmp notation
|
||||
ALTEON-TIGON-SWITCH-MIB::agSoftwareVersion.
|
||||
|
||||
When choosing the name for the methods, be aware that other new
|
||||
Sub Modules might inherit this one to get it's features. Try to
|
||||
@@ -2016,9 +2022,15 @@ the SNMP::Info methods.
|
||||
|
||||
=item %FUNCS
|
||||
|
||||
Contains a hash in the form ( method_name => SNMP iid)
|
||||
Contains a hash in the form ( method_name => SNMP MIB leaf name)
|
||||
These are table entries, such as the IfIndex
|
||||
|
||||
To resolve MIB leaf name conflicts between private MIBs, you may prefix the
|
||||
leaf name with the MIB replacing each - (dash) and : (colon) with
|
||||
an _ (underscore). For example, ALTEON_TS_PHYSICAL_MIB__agPortCurCfgPortName
|
||||
would be used as the hash value instead of the net-snmp notation
|
||||
ALTEON-TS-PHYSICAL-MIB::agPortCurCfgPortName.
|
||||
|
||||
=cut
|
||||
|
||||
%FUNCS = (
|
||||
|
||||
Reference in New Issue
Block a user