| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2247.1 | QAR 2245 | TOOK::MINTZ | Erik Mintz, DECmcc Development | Fri Jan 31 1992 11:45 | 2 |
| QAR 2245 in MCC_INTERNAL
|
| 2247.2 | Do not use RDB files created by MCC V1.1 | TOOK::SHMUYLOVICH | | Fri Jan 31 1992 13:43 | 17 |
|
Rdb schema in MCC V1.2 is different from V1.1.
You can not export data using MCC V1.2 into Rdb file created by
MCC V1.1. Also you can not run Reports from V1.2 against Rdb files
created in V1.1.
Is there a reason you want to keep an old(from V1.1) and new
(from V1.2) data together in the same Rdb file or you just ran into
this problem by accident?
If you think that it's very important to make data exported in
V1.1 and in V1.2 compatible we'll try to provide a conversion
procedure.
SAm
|
| 2247.3 | problem with history/export/reports | NYFDIN::SAMBAMURTY | Raja | Tue Feb 04 1992 16:45 | 26 |
| I too am running T1.2 on a VS3100/16Meg/VMS5.4-3 and have not been able
to produce any DTR reports. I did all the steps that are outlined in
the manual.
1) I start the background job for record with the domain name as the
parameter, start to record attributes (counters) on a given router (line,
circ & node).
2) after 24 hrs, I start the exporter in the background (I have defined
MCC_EXPORT in DTR, have my CDD$DEFAULT pointing to my CDD dir) with the
name of the rdb file as a parameter. Then I start to "record". The rdb
file gets created (the size is about 3100 blocks for the .rdb file). At
this point I run the mcc_rpts file to generate hourly circuit info,
line & node traffic info and all the 3 files get created but there is
nothing in the files (they are all 0/0 size).
I would appreciate if someone can point me in the right direction (if
you think I am doing something wrong). Also, I can't seem to delete the
.rdb files from the V1.1 of MCC. (I try
RDO> delete database path 'blah'.
and I get back something about having to invoke a database first.
Is this facility known to work in theis version ? Any help would be
appreciated. Thanks
Raja
|
| 2247.4 | | NYFDIN::SAMBAMURTY | Raja | Thu Feb 06 1992 13:17 | 14 |
| I still haven't figured out as to why this doesn't work. Someone told
me to key the node address instead of the node name and it still
doesn't seem to work. I know the export works and the DB is getting
populated (I did a
RDO> for j in mcc_node4_circuit
cont> print j.*
cont> end_for
)
and prints out fields and their stored values. Any help would be
appreciated. Thanks.
Raja
|
| 2247.5 | some help coming, hopefully | TOOK::CALLANDER | MCC = My Constant Companion | Thu Feb 20 1992 19:51 | 2 |
| your request for help has been forwarded to Sam
he should be getting back to you.
|
| 2247.6 | See note 2315.* | TOOK::ANWARUDDIN | Anwar | Fri Feb 21 1992 09:43 | 1 |
| Note 2315.* answers the questions in .4
|
| 2247.7 | | NYFDIN::SAMBAMURTY | Raja | Fri Feb 21 1992 11:06 | 16 |
| � Note 2315.* answers the questions in .4
Indeed, it did and they work better now. There are still a lot problems
with the reports. (1) One of the most glaring ones is, the word out is
capitalized in one place and not in the other (I know it is trivial,
but that was one of the first things the customer noticed). (2)
Sometimes I see that circuit syn-0 was polled n times and was
successful n-2 (or3) times. Why would the polling fail (both the mcc
station and the router are on the same ethernet and neither of them
went down during the polling period) ? (3) the peak times/dates as
reported by the reports is still a suspect (and at times inconsistent,
i.e. sometimes it prints just the date and other times, date/time
combo). And last (but not least), the exporter is very, very slow (as I
have pointed out in another note). Thanks for your time.
Raja
|
| 2247.8 | | TOOK::ANWARUDDIN | Anwar | Tue Mar 24 1992 09:41 | 43 |
|
� Note 2315.* answers the questions in .4
Indeed, it did and they work better now. There are still a lot problems
with the reports. (1) One of the most glaring ones is, the word out is
capitalized in one place and not in the other (I know it is trivial,
but that was one of the first things the customer noticed).
************ OK
(2) Sometimes I see that circuit syn-0 was polled n times and was
successful n-2 (or3) times. Why would the polling fail (both the mcc
station and the router are on the same ethernet and neither of them
went down during the polling period) ?
************ This means that the Exporter got back an exception from a MM.
************ You can tell by looking at two fields "exp_cvr_<partition_name>"
************ & "exp_cvr1_<partition_name>" in the tables. These fields are
************ in every partition. The values that are valid for the first
************ field are:
************ 1 = reposponse (success)
************ 2 = mcc_error
************ 3 = Common Exception
************ 4 = Specialized Exception
************ The field "exp_cvr1_<partition_name>" will contain one of the following:
************ reposponse id , if successful (value 1)
************ error code (defined in mcc_msg.h)
************ exception code in case of Common Exception or a Specialized exception.
************ The code is looked up from the data dictionary.
************ If both fields have the value 1, the poll succeeded. Otherwise the poll
************ failed.
(3) the peak times/dates as
reported by the reports is still a suspect (and at times inconsistent,
i.e. sometimes it prints just the date and other times, date/time
combo). And last (but not least), the exporter is very, very slow (as I
have pointed out in another note). Thanks for your time.
*********** Regarding the peak dates/times, I believe Meera spoke to you.
Raja
|