| Solstice Enterprise Manager 4.1 Installation Guide | |
Data Definition Files
The Solstice Enterprise Manager (Solstice EM) software includes GDMO and ASN.1 files that store object definitions in the Management Information Server (MIS). These files can be categorized as follows:
- Files required to run the MIS
- Files that are extensions of the SNMP MIB-II or files for specific vendor's devices
- Files required to run the SunNet Manager (SNM) RPC agents
The files in the first two categories are part of the Solstice EM MIS package (SUNWemmis), while the files in the third category are part of the SNM Compatibility package (SUNWembc).
This chapter lists the GDMO and ASN.1 files in each category, and provides instructions on how you can improve the Solstice EM MIS startup time by moving some of the GDMO and ASN.1 files.
The Solstice EM software also includes additional third-party MIBs that you can compile using the Load Data Definitions tool.
This chapter describes the following topics:
- Section C.1 Files Required for the MIS
- Section C.2 Extensions to SNMP-MIB II and Vendor-Specific Files
- Section C.3 Files Required for SNM RPC Agents
- Section C.4 Improving the MIS Startup Time
- Section C.5 Third-Party MIBs
C.1 Files Required for the MIS
C.1.1 GDMO Files
The following GDMO files are required for the MIS:
- anno.gdmo
- coll.gdmo
- d3.gdmo
- dmi.gdmo
- iimcIIMCProxy.gdmo
- iimcManagementDoc-1.gdmo
- map.gdmo
- mpa.gdmo
- nc-d3.gdmo
- nc.gdmo
- rfc1213.gdmo
- rfc1155.gdmo
- security.gdmo
- topo.gdmo
- vol1.gdmo
- vol4.gdmo
C.1.2 ASN.1 Files
The following ASN.1 files are required for the MIS:
- IimcAssignedOIDs.asn1
- IimcCommonDef.asn1
- IimcProxyASN1.asn1
- acse.asn1
- anno.asn1
- any.asn1
- asn1.asn1
- cnm.asn1
- coll.asn1
- d3.asn1
- dmi.asn1
- evr2oc.asn1
- infofw.asn1
- map.asn1
- mpa.asn1
- nc-d3.asn1
- nc.asn1
- rfc1213TYPE.asn1
- security.asn1
- topo.asn1
- test.asn1
- usefuldef.asn1
- vol1.asn1
- vol2.asn1
- vol4.asn1
- x711.asn1
C.2 Extensions to SNMP-MIB II and Vendor-Specific Files
C.2.1 GDMO Files
The following GDMO files are extensions to MIB-II or are vendor-specific:
- 3com.gdmo
- cisco.gdmo
- retix-remote-bridge.gdmo
- sun.gdmo
- synoptics.gdmo
C.2.2 ASN.1 Files
The following ASN.1 files are extensions to MIB-II or are vendor-specific:
- 3comTYPE.asn1
- ciscoTYPE.asn1
- retix-remote-bridgeTYPE.asn1
- sunTYPE.asn1
- synopticsTYPE.asn1
C.3 Files Required for SNM RPC Agents
C.3.1 GDMO Files
The following GDMO files are required if you plan to use the SNM RPC agents in the SUNWsnmag package:
- diskinfo.gdmo
- centillion-elements-schema.gdmo
- cisco-elements-schema.gdmo
- cooptools-schema.gdmo
- elements-schema.gdmo
- netware-elements-schema.gdmo
- switch-elements-schema.gdmo
- syn-multimedia-switch-schema.gdmo
- synoptics-elements-schema.gdmo
- synoptics-lcell-schema.gdmo
- synoptics-stackprobe-schema.gdmo
C.3.2 ASN.1 Files
The following ASN.1 files are required if you plan to use the SNM RPC agents in the SUNWsnmag package:
- diskinfo.asn1
- centillion-elements-schema.asn1
- cisco-elements-schema.asn1
- cooptools-schema.asn1
- elements-schema.asn1
- netware-elements-schema.asn1
- switch-elements-schema.asn1
- syn-multimedia-switch-schema.asn1
- synoptics-elements-schema.asn1
- synoptics-lcell-schema.asn1
- synoptics-stackprobe-schema.asn1
C.4 Improving the MIS Startup Time
MIS startup is considerably faster if you use only the required GDMO and ASN.1 files. If you want to have less than the full complement of GDMO and ASN.1 files compiled into your MIS at startup, you must move the unnecessary files to a different directory after the installation is complete. The GDMO and ASN.1 files are stored in $EM_HOME/etc/gdmo and $EM_HOME/etc/asn1, respectively.
To Move the GDMO/ASN.1 Files
Caution – The following procedure permanently removes all data from the MIS, including managed objects and discovery data. If you have not made a backup copy of data, it is recommended that you do so before deleting any data.
Also, it is strongly recommended that you export topology information to a file. Additionally, you may want to export request templates, conditions, poll rates, and severities. For more information on using the import/export tool, refer to Chapter 5 in Management Information Server Guide.
1. Move the unnecessary GDMO and ASN.1 files to a different directory.2. To start the MIS, recreate the entire database, and recompile all MIBs, type the following command in a shell or command tool:
- /opt/SUNWconn/bin/em_services -reload
Note – If you installed the product in a different directory, substitute your partition name for /opt.
- The prompt asks if you want to delete all data from the database.
3. When prompted to delete all database information, type y to continue, or n to return to the shell prompt.
- The system performs the following actions:
- stops the database server and removes all data, including the schema files associated with the GDMO and ASN.1 files you moved
- Instantiates the object definitions for objects described in $EM_HOME/etc/gdmo, $EM_HOME/etc/asn1, and /var/$EM_HOME/data
- recreates the directory and database structure
- recompiles and reloads MIBs
- recreates database tables and indexes
- restarts Solstice EM daemons
4. Re-import the data.C.5 Third-Party MIBs
The Solstice EM software includes additional third-party MIBs that you can compile using the Load Data Definitions tool. For information on compiling these MIBs into GDMO files in the MIS, refer to Chapter 8 in Management Information Server Guide..
|
Sun Microsystems, Inc. Copyright information. All rights reserved. |
Doc Set | Contents | Previous | Index |