From b03e292d95715cf88bd2c445632dec4c90219dec Mon Sep 17 00:00:00 2001
From: Eric Miller <>
Date: Mon, 21 Apr 2008 20:55:52 +0000
Subject: [PATCH] Document fully qualifying a MIB leaf in %GLOBALS and %FUNCS

---
 Info.pm | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/Info.pm b/Info.pm
index 1b5c82d1..de05dc0a 100644
--- a/Info.pm
+++ b/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   = (