Cabletron Systems MRXI-2 Guide de l'utilisateur Page 85

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 116
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 84
For the purposes of this exercise, we will use rfc1213.mib, which is a file containing the definition of MIB-II.
Assuming you have installed SAS and the IT Service Vision server in /usr/local/sas, you can find a copy of
rfc1213.mib in /usr/local/sas/saspgm/cpe/mibs/.
Actions
1. Compile the MIB.
In this action we are going to compile rfc1213.mib and produce two output files: rfc1213.ddu and rfc1213.sas. The
.ddu file will contain the CPDDUTL control statements needed by the %CPDDUTL macro. The .sas file will contain
the PROC FORMAT statements needed to create the formats for enumeration types.
To compile the MIB, execute the following command (assuming that SAS has been installed in /usr/local/sas and
that your
PATH
includes
/usr/local/sas/utilities/bin/
):
mib2dict -i rfc1213.mib -o rfc1213.ddu -f rfc1213.sas -c hp-ov
where
the -i option specifies rfc1213.mib as the input file to be compiled. If you do not specify -i, then
mib2dict will expect input from stdin.
the -o option specifies rfc1213.ddu as the output file to which CPDDUTL control statements are printed. If
you do not specify -o, CPDDUTL control statements will print to stdout.
the -f option specifies that rfc1213.sas is to receive the SAS statements for PROC FORMAT. If you do not
specify
-f
, then no PROC FORMAT statements are written to
rfc1213.sas
.
Note: When you specify the -f option, any CPDDUTL CREATE VARIABLE statements that are generated by
mib2dict have a FORMAT= parameter that is set to the proper SAS format, as defined in rfc1213.sas. In a
later action, you will execute rfc1213.sas. If you do not execute rfc1213.sas, the formats will not exist
and you will receive format errors when a value that uses the non-existent format is to be displayed.
the -c option specifies what hp-ov as the collector to use. If you do not specify -c, the collector will be set to
an empty string.
Note:
When you specify the
-c
option, any CPDDUTL CREATE TABLE statements that are generated by
mib2dict
have a COLLECTOR= parameter that is set to
hp-ov
. In this example we use
hp-ov
because we
plan to use HP OpenView Network Node Manager or IBM NetView for AIX to collect the SNMP data. You may
use any collector supported by IT Service Vision that can collect SNMP data. Or if you are logging SNMP data
in an unsupported format, you could use -c
generic and use the IT Service Vision generic collector capability
to read the raw data.
2. Review, and revise if necessary, the resulting CPDDUTL control statements.
Although mib2dict is designed to create CPDDUTL control statements that can be directly processed by the
%CPDDUTL macro, there are circumstances in which you may want to edit the control statements before you use them:
1. There may be tables or variables that were in the MIB but that you do not want to add to your PDB .
If this is the case, prior to executing the %CPDDUTL macro you can simply delete the CPDDUTL control
statements that define the tables or variables that you do not want.
To delete an entire table, look for the CREATE TABLE statement and delete everything up to the next CREATE
TABLE statement.
To delete a variable from a table, simply delete everything from CREATE VARIABLE up to and including the
semicolon that ends the statement.
If you delete a variable from a table but you do not delete the entire table, be sure that the variable you deleted is
Vue de la page 84
1 2 ... 80 81 82 83 84 85 86 87 88 89 90 ... 115 116

Commentaires sur ces manuels

Pas de commentaire