{"id":75,"date":"2016-01-01T19:06:22","date_gmt":"2016-01-01T13:36:22","guid":{"rendered":"http:\/\/www.middlewareprimer.com\/blog\/?p=75"},"modified":"2016-01-01T19:06:22","modified_gmt":"2016-01-01T13:36:22","slug":"ibm-websphere-datapower-mib-and-oid-information","status":"publish","type":"post","link":"http:\/\/www.middlewareprimer.com\/blog\/2016\/01\/01\/ibm-websphere-datapower-mib-and-oid-information\/","title":{"rendered":"IBM Websphere Datapower MIB and OID Information"},"content":{"rendered":"

IBM Websphere Datapower MIB and OID Information<\/p>\n

SNMP managers rely on MIBs to define the specific details that are related to the devices that are being managed. Each object (or characteristic) has a unique OID consisting of a series of numbers separated by decimal points.<\/p>\n

SNMP itself does not define which information, or variables, a managed system needs to offer. Rather, the available information is defined within Management Information Bases (MIBs). MIBs are text files that describe the structure of the device\u2019s management data using a hierarchical namespace containing object identifiers (OIDs). Each OID identifies a specific metric that can be queried (or sometimes set) via SNMP.<\/p>\n

How do we get MIBs in Datapower? How do we identify the OIDs? Below information will give you a brief idea on the same.<\/p>\n

Refer to Enable SNMP<\/a><\/strong><\/span> post written earlier and download the 3 text files. By enabling SNMP in Datapower, 3 files will be given for us to download which contain information about OIDs. Open drStatusMIB.txt file using any editor.<\/p>\n

\"IBM<\/p>\n

 <\/p>\n

drStatusMIB contains a structured format of Object Identifiers. Each object (or characteristic) has a unique
\nOID consisting of a series of numbers separated by decimal points. Below screenshot for reference for a standard format structure identified in Datapower.<\/p>\n

1.3.6.1.4.1.14685.3.1 –> Consider this as a standard value for Identifying the Datapower System Characteristics.<\/p>\n

\"IBM<\/p>\n

 <\/p>\n

Once this value is taken out, we need to identify the OIDs hierarchy for specific Monitoring tasks. dpStatus along with specific Object Identifier gives us a numeric format. Consider, dpStatusSystemUsage is the Object Identifier which we are planning to Monitor. Below screenshot gives you an idea on how we identify the OID numeric values. Every OID now contains object types associated with it.<\/p>\n

\"IBM<\/p>\n

 <\/p>\n

dpStatusSystemUsage is the Object Identifier and dpStatusSystemUsageInterval is one of the Object type. Each Object Identifier will contain a dpStatus<\/strong> and this will be starting point to identify the OIDs. So for dpStatusSystemUsage Object Identofier following numeric values will be considered. There will be a proper description given to each OID.<\/p>\n

1.3.6.1.4.1.14685.3.1.52\u00a0\u00a0 \u00a0\u00a0dpStatusSystemUsage<\/p>\n

1.3.6.1.4.1.14685.3.1.52.1\u00a0\u00a0dpStatusSystemUsageInterval<\/p>\n

1.3.6.1.4.1.14685.3.1.52.2\u00a0 dpStatusSystemUsageLoad<\/p>\n

1.3.6.1.4.1.14685.3.1.52.3\u00a0 dpStatusSystemUsageWorkList<\/p>\n

\"IBM<\/p>\n

 <\/p>\n

As an Example, for below Object Identifiers we have specific Numeric values assigned. The same values can be taken out for rest of all the Object Identifiers.<\/p>\n

SystemUsage\u00a0\u00a0 dpStatusSystemUsageLoad\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1.3.6.1.4.1.14685.3.1.52.2
\nCPUUsage\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0dpStatusCPUUsagetenSeconds\u00a0\u00a0 1.3.6.1.4.1.14685.3.1.14.1
\nMemoryStatus\u00a0\u00a0dpStatusMemoryStatusUsage\u00a0\u00a0\u00a0\u00a0\u00a0 1.3.6.1.4.1.14685.3.1.5.1
\nSystemUpTime dpStatusDateTimeStatusuptime\u00a0\u00a0 1.3.6.1.4.1.14685.3.1.3.2<\/p>\n

Configure these SNMP values in any monitoring software. Some of the content and MIB image are taken from Datapower Redbook<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

IBM Websphere Datapower MIB and OID Information SNMP managers rely on MIBs to define the specific details that are related to the devices that are being managed. Each object (or characteristic) has a unique OID consisting of a series of numbers separated by decimal points. SNMP itself does not define which information, or variables, a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[42,46,44,45,47,43],"class_list":["post-75","post","type-post","status-publish","format-standard","hentry","category-ibm-websphere-datapower","tag-datapower","tag-datapower-monitoring","tag-mib","tag-oid","tag-snmp-in-datapower","tag-websphere-datapower"],"_links":{"self":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/75","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/comments?post=75"}],"version-history":[{"count":3,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/75\/revisions"}],"predecessor-version":[{"id":212,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/75\/revisions\/212"}],"wp:attachment":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/media?parent=75"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/categories?post=75"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/tags?post=75"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}