|Oracle® Communications Network Integrity Developer's Guide
|PDF · Mobi · ePub|
This chapter describes the SNMP (Simple Management Network Protocol) processor, which is one of two processor types supported by the discovery action in Network Integrity.
The SNMP Processor is a completely implemented processor that polls SNMP-enabled network devices using the SNMP protocol.
The other supported processor is the discovery processor, which is a general processor, and has no concrete implementation; it can be implemented using Design Studio to discover network data through various technologies and protocols (for example, TL1 and CORBA) or to model discovered data and persist the data in the Results Model. See "Configuring a Discovery Processor".
See "Working with Discovery Actions and Processors" for general information about discovery actions and supported processors.
There are several ways to create an SNMP processor. However, the best way is to create it using the Processor tab for the discovery action. This method automatically adds the processor to the list of processors that the action uses. And it also ensures that only the supported type of processor is created for the current action.
To create a processor, see Network Integrity Studio online Help.
Note:Discovery actions support two types of processor: discovery processor and SNMP processor. In the Processor Wizard, the Type field is enabled. Ensure SNMP Processor is selected when creating an SNMP processor.
When you create an SNMP processor and add it to a Discovery action, a code-generated SNMP UI parameter is automatically added to this Discovery action (available in the "UI Parameters" tab in the Discovery Action Editor).
Note:Do not modify this code-generated SNMP UI parameter in the Data Dictionary Editor. If you must extend the SNMP UI parameter, create a UI parameter instead of modifying the code-generated SNMP UI parameter.
The SNMP Processor is a code-generated Discovery processor with the complete implementation. The SNMP Processor polls an SNMP-enabled network device by sending a request containing a list of OIDs (and other relevant SNMP configurations) to the SNMP Adapter, and receiving the response containing a strongly-typed XML document, which represents the raw SNMP results. There is no coding required for the SNMP processor. The Processor Interface, Request/Response, Properties, and the relevant helper classes of an SNMP Processor are all code -generated and fully implemented.The only configuration required for the SNMP Processor is to configure the list of polled OIDs. Before configuring the OIDs for the SNMP Processor, the MIB directory must be properly specified for the Network Integrity preference. If the MIB directory is not properly specified in the preference, you cannot configure the SNMP processor.
See "Setting Preferences in Network Integrity" for more information.
When the list of polled OIDs has been configured, the selected MIBs are available.
Figure 7-1, displays two MIBs, ATM-MIB and RFC1213-MIB, as selected.
The SNMP processor is a completely code-generated discovery processor. Along with the usual discovery processor implementations (see "Implementing a Discovery Processor"), Design Studio also generates the strongly-typed SNMP XML response document schema based on the OIDs configured for the SNMP processor.
The generated SNMP XML response document schemas are available at the following directory:
Under this directory, the following sub-directories exist:
lib: this directory contains the compiled XML Beans JAR file for the strongly-typed SNMP XML response document schemas
snmpClasses: this directory contains the XML Beans Java classes for the strongly-typed SNMP XML response document schemas
snmpSchemas: this directory contains the generated strongly-typed SNMP XML response document schemas
snmpSrc: this directory contains the compiled XML Beans Java source for the generated strongly-typed SNMP XML response document schemas.
It is recommended to first look at the schemas generated in this directory to understand how to access the compiled XML Beans object for the SNMP response document.
The remaining implementations for the SNMP Processor are at the following directory:
The SNMP Processor always has an output parameter, which is the SNMP XML response document (XML Beans object). This is available in the Response class for the SNMP processor.
When the productized Network Integrity cartridges are imported into Design Studio (see "Exporting and Importing Cartridges"), Network Integrity cartridges are bundled with a set of MIB files, which is the same set of MIB files bundled with the SNMP Resource Adapter (see "JCA Resource Adapters").
If you must create a Network Integrity cartridge to poll certain MIB OIDs for certain specific devices, which are not part of the bundled MIB files, you must get the MIB file (or set of MIB files) that has the definitions of those MIB OIDs required to implement the new cartridge.
The new MIB files must be manually copied to the MIB directory configured in the Design Studio preference (see "Setting Preferences in Network Integrity"). After the new MIB files are copied to the MIB directory, the new MIB files are available to be loaded in Studio. There is no need to restart Design Studio.
Note:The MIB files on Studio and on the SNMP resource adapter must match. See "JCA Resource Adapters" for information about supporting new MIBs for the SNMP resource adapter.