|
RE: .1:
> 1. Starting the EXPORTING from decw. PM is just hanging and
> the process is staying in RWBMX state and nothing is happening.
> 2. Starting it from the form. PM is giving me problems
> either with the qualifiers or the way I use the begin or end
> time. I tested the past time as:
> a) 14-feb-1991 12:00 or (14-feb-1991 12:00) or
> 14-feb-1991:12:00 or 14-feb-1991:12:00.0
> Can you tell me what I'm doing wrong.
> Can you help me with the right syntax for geting the past data.
The only difference between future and past time Export is
IN DOMAIN qualifier. For past Export you must specify a Domain where
historical data have been stored. Decw interface provides IN DOMAIN
automatically but from FCL you have to specify it in the command line.
According to the specified time arguments Exporter decides if
this is a past or future time request. Please, note that begin and
end time have to be entered as arguments to the Export directive but
not as scope of interest time.
The syntax for Export directive is:
EXPORT SNMP name [EXPORT TARGET = rdb_file_name]
[,BEGIN TIME = DD-MMM-YYYY HH:MM:SS]
[,END TIME = DD-MMM-YYYY HH:MM:SS]
[,EXPORT PERIOD = D HH:MM:SS]
[,SEQUENCE NAME = name]
[,SEQUENCE NUMBER = number]
,IN DOMAIN domain_name <-- required for the past time
Note:
- all arguments are optinal;
- arguments must be separated by comma.
Defaults:
- BEGIN TIME = NOW;
- END TIME = NEWER;
- EXPORT PERIOD = 1 day;
- SEQUENCE NAME = EXPORT;
- SEQUENCE NUMBER = 0.
It would be easier to say what is wrong in your case if you give us
error massages you had.
> Doing the SHOW RECORDING is showing that data has been collected.
The better way to be sure that historical data have been
collected is to do past time show.
> Is it right understood that for EXPORTING past data we do not
> use the background process?
It's correct. If you have a lot of past data to Export it
can take some time while you get back MCC prompt.
> One other thing with the RDB file; I was EXPORITING the SNMP entity
> EXPORT SNMP LWRTR1 INTERFACE 1 and it is working ok but the information
> or the records do not have any information about the entity name,
> in my case the LWRTR1. And if I would EXPORT more entities into
> the same RDB file then I would have problem diffrentiating the
> entities.
Unfortunately Exporter in the V1.1 does not support data types
which are used for SNMP identifiers. It will be fixed in V1.2.
For now I can recommend using SEQUENCE NAME argument of the Export
directive. This argument has data type Latin1String (its default
value is "EXPORT") and is exported to the RDB file together with
the entity's attributes. When the user enters Export directive for
SNMP he is able to specify SEQUENCE NAME as a SNMP instance,for example,
EXPORT SNMP name_1 EXPORT TARGET = rdb_file.rdb, SEQUENCE NAME = name_1
EXPORT SNMP name_2 EXPORT TARGET = rdb_file.rdb, SEQUENCE NAME = name_2
In this example the column SEQUENCE in the RDB table will have value
"name_1" for SNMP name_1 and "name_2" for SNMP name_2.
... Does any one of you
> have DECDECISION macros that would be nice to share and would eas
> our job?
As I know answer is no.
Sam
|