-- Performance Monitoring Tables
genEquipPmRfuCommonSL15minMinRsl OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This value indicates the minimum RSL value."
::= { genEquipPmRfuCommonSL15minEntry 4 }
genEquipPmRfuCommonSL15minMaxRsl OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This value indicates the maximum RSL value."
::= { genEquipPmRfuCommonSL15minEntry 5 }
genEquipPmRfuCommonSL15minMinTsl OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This value indicates the Min TSL value."
::= { genEquipPmRfuCommonSL15minEntry 8 }
genEquipPmRfuCommonSL15minMaxTsl OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This value indicates the Max TSL value."
::= { genEquipPmRfuCommonSL15minEntry 9 }
Follows the template creation in order:
- - Data Templates
- - Host Templates
- - Graph Templates
As We want to place all the information in the same graph, four "Data Templates" are going to be created (Min RSL, Max RSL, Min TSL and Max TSL)
and here's the contents of each "Data Templates" Soon We hit the create button, another set of fields shows up which allow us to insert What really means a lot to the system. Specifically talking about the object identifier or OID for short.
We use the MIB information provided above to gather the information and fill in the blanks.
If We translate the OID, We get exactly the info above (from the MIB file)
me@2pacalypse:~$ snmptranslate -m /usr/local/share/snmp/mibs/CERAGON-MIB_6.6.1.15.txt -Td .1.3.6.1.4.1.2281.10.6.1.1.1.1.4.1
AIDU-MIB::genEquipPmRfuCommonSL15minMinRsl.1
genEquipPmRfuCommonSL15minMinRsl OBJECT-TYPE
-- FROM AIDU-MIB
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION "This value indicates the minimum RSL value."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ceragon(2281) genEquip(10) genEquipPM(6) genEquipPmRfu(1) genEquipPmRfuCommon(1) genEquipPmRfuCommonSL15minTable(1) genEquipPmRfuCommonSL15minEntry(1) genEquipPmRfuCommonSL15minMinRsl(4) 1 }
me@2pacalypse:~$
Then, if We walk We get a "NEGATIVE" value which varies slightly. That's the actual RSL.
Obviously We require the numerical value of each OBJECT-TYPE and for the reason being We use the -On flag.
me@2pacalypse:~$ man snmpcmd
::OUTPUT SUPRESSED
-On Displays the OID numerically:
::OUTPUT SUPRESSED
me@2pacalypse:~$ snmpwalk -m /usr/local/share/snmp/mibs/CERAGON-MIB_6.6.1.15.txt -On -v 1 -c public 10.222.11.40 genEquipPmRfuCommonSL15minMinRsl
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.1 = INTEGER: -50
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.2 = INTEGER: -50
:: OUTPUT SUPRESSED
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.9 = INTEGER: -50
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.10 = INTEGER: -51
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.11 = INTEGER: -50
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.12 = INTEGER: -51
:: OUTPUT SUPRESSED
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.46 = INTEGER: -49
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.47 = INTEGER: -49
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.48 = INTEGER: -50
:: OUTPUT SUPRESSED
.1.3.6.1.4.1.2281.10.6.1.1.1.1.4.96 = INTEGER: -50
me@2pacalypse:~$
Note: As RSL measurements are NEGATIVE values in dBm therefore, We also changed the Minimum and Maximum Value from Its defaults.
That's ALL for the Data Templates.
Note: The same applies for the remaining object types
Continues in the next post...