| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
MCC documentation is confusing me. Why doesn't it use MCC command
component topics when discribing things? Can somebody help me out
here? I am trying to set up recording so that I may later get
statistics on a one paticular line (syn-0). I have benn recording line
counter, characteristics, and circuit counter. When I ask for the
statistics, MCC tells me the following.
SHOW NODE4 M1LN03 LINE SYN-0 INBOUND UTILIZATION, OUTBOUND UTILIZATION,
INBOUND
BLOCK RATE, OUTBOUND BLOCK RATE, IN DOMAIN .MKO.DOMAIN.NEI-NH, FOR
START 12:45
duration 00:15
Node4 M1LN03 Line SYN-0
AT 25-MAY-1993 13:00:00 Statistics
Node4 DEC:.mko.m1ln03 Circuit ETHERNET Characteristics not available
for
specified time.
So I read the PA FM use guide. It says that in order to compute DDCMP
link entity statistics, I need to record all attribute partions for the
following:
"The link entity, the logical station child entity, and the modem
connect line entity corresponding to the link"
What the heck does this mean? Is the link entity supposed to be line,
circuit, both, or something else? What is the logical station child
entity, and what is the modem connenct line entity????
help... MCC doesn't make things easy.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5115.1 | You have specified a Phase-4 entity | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue May 25 1993 16:36 | 20 |
RE .0
>> SHOW NODE4 M1LN03 LINE SYN-0 INBOUND UTILIZATION, -
>> OUTBOUND UTILIZATION, INBOUND BLOCK RATE, OUTBOUND BLOCK RATE, -
>> IN DOMAIN .MKO.DOMAIN.NEI-NH, FOR START 12:45 duration 00:15
You have specified a "Phase-4 Line" entity (Node4/Line) ... Exhibit 2-3
of the PA use manual (dated Feb-93) says that you must have recorded
all attribute partitions for:
the Line and for ALL Circuits on that Line.
I believe you read the section on "Phase-5 DDCMP Link" entities .. thats
probably where the confusion came from.
IMHO .. wouldn't it make sense for the Historical Data Recorder to be
able to ask the Performance Analyzer what kinds of data need to be
recorded for which statistics .. and take the human out of the loop.
/keith
| |||||
| 5115.2 | All- I'll run out of disk space!! Why? | ABACUS::BUKOWSKI | Tue May 25 1993 17:46 | 21 | |
RE. -1
Yes it sure would be nice if something told you in plain english what
needed to be recording. It doens't even have to be fancy, just a
little list like:
- all line charateristics, all line counters
- all cir charateristics, all cir counters
etc..
BTW: are you sure that I need all partition for circuits and line to
get a simple inbound utilization on one specific DDCMP line? The
formula only asks for: bs + hs *dbs
-------------- *bits * 100
speed*time
These values are available from syn-0 circuit count and line syn-0
charateristics. Why does it need partitions like identifiers and
status?
Mike
| |||||
| 5115.3 | Why does PA need "All Idents" .. ? | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Wed May 26 1993 10:06 | 10 |
I believe that PA first does a "Show <entity> * All Ident" .. then for each entity instance returned creates a thread to fetch the counters. Please don't ask why this was done this way .. the guy that wrote the code is loooooonng gone .. I'm just the happy engineer to pick up the pieces. I can double check the tables to see exactly what attributes go into the DDCMP Line Inbound & Outbound Utilization .. you never know, the documentation could be wrong. /keith | |||||
| 5115.4 | working with fewer than all partitions | ABACUS::BUKOWSKI | Wed May 26 1993 10:57 | 8 | |
Well, I got the stats working for syn-0 by recording counters and
characteristics on on Ethernet and syn-0 line and circuits. That is
a few less partitions than all.
BTW Keith, thanks for that PA executable, the bridge line utils work
great..!
Mike
| |||||
| 5115.5 | What PA needs for Node4/Line stats when the protocol is DDCMP | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Wed May 26 1993 11:09 | 31 |
RE: .4
PA has a log bit which will dump out the Entities polled for attribute data.
define mcc_pa_fm_log 40
For -- SHOW NODE4 M1LN03 LINE SYN-0 all statis, for dur 00:00:20
PA gets data from:
Line syn-0 all characteristics
Line syn-0 all counters
Circuit * all identifiers
Circuit ethernet all characteristics
Circuit syn-0 all characteristics
>> Well, I got the stats working for syn-0 by recording counters and
>> characteristics on on Ethernet and syn-0 line and circuits. That is
>> a few less partitions than all.
But you did not record any Identifiers .. ? That makes me wonder.
I'll have to poke around the code (yuck) to see what's going on when
fetching the Identifiers.
>> BTW Keith, thanks for that PA executable, the bridge line utils work
>> great..!
Good 8) 'bout time - huh ?
/keith
| |||||
| 5115.6 | iden not needed for *circuit* stats | CTHQ::WOODCOCK | Wed May 26 1993 11:23 | 17 | |
Hi there, > But you did not record any Identifiers .. ? That makes me wonder. > I'll have to poke around the code (yuck) to see what's going on when > fetching the Identifiers. We have never RECORDed identifiers to get stats but... We issue stat commands for the CIRCUIT: show node4 x CIRCUIT syn-0 all statis Maybe there is a difference between asking for LINE and CIRCUIT stats for getting info like utilization. And maybe one is more efficient than the other. best regards, brad... | |||||
| 5115.7 | Node4/Circuit Statistics | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Wed May 26 1993 14:46 | 15 |
re: .6 > We have never RECORDed identifiers to get stats but... We issue stat commands > for the CIRCUIT: > > show node4 x CIRCUIT syn-0 all statis > > Maybe there is a difference between asking for LINE and CIRCUIT stats for > getting info like utilization. And maybe one is more efficient than the other. Just checked the PA tables and Node4/Circuit Statistics do no require Identifier attributes ... But Node4/Line stats do. /keith | |||||
| 5115.8 | which partition, how often? | ABACUS::BUKOWSKI | Thu May 27 1993 09:05 | 9 | |
Well i do not know if this may be of any help, but for about 1 hour,
when I started this mis-adventure, I started recording for all
partitions, on all circuits and lines. From what Brad was telling me,
the PA seems to get the identifiers from the time closest to the
requested statistics. Do you think the PA is looking back two days
for my identifiers???
Mike
| |||||
| 5115.9 | Help Mr. Wizard!! | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Thu May 27 1993 09:17 | 16 |
re .8 > From what Brad was telling me, the PA seems to get the identifiers > from the time closest to the requested statistics. Do you think > the PA is looking back two days for my identifiers??? I can't say for sure .. I think that PA always checks the timestamps of the data, so two day old Identifiers wouldn't fit well with todays counters .. I would expect some kind of error message (may not be telling you exactly what is wrong though). If you cross your fingers I might be able to find something in the code that makes some sense. I'm currently working on PA so I've got the hood up and can poke around a bit. /keith | |||||
| 5115.10 | clarification please! | KERNEL::WARDJO | Fri Jan 21 1994 06:52 | 29 | |
Hello,
Can anyone clarify what needs to be recorded inorder to get
utilization for line syn-0. Am I correct in assuming that all line and
circuit info is required for syn-0 & ethernet.
If this is so can anyone explain why ethernet information is required
when only syn-0 utilization is required.
A customer has been happily recording line and circuit info for sny-0
every 15 minuites for the last month and now gets the message "Node4
LOCAL_NS:.decrtr4 Circuit ETHERNET Characteristics not available for
specified time". Is the info he has recorded so far totally useless?
He was not happy when I suggested he needs to record the ethernet info
as well and commented that "it is unuseable if that is the case" - he
wants to record data for 3 months and does not have the disk space
required to record ethernet info aswell.
He also commented that he does not require ethernet info for sysco
routers.
Can anyone help - the customer is very unhappy.
Regards,
Jon
| |||||
| 5115.11 | SYN does not need ETHERNET | CTHQ::WOODCOCK | Skiing's 1st Human Groomer | Mon Jan 24 1994 10:30 | 30 |
Greetings, > Hello, > > Can anyone clarify what needs to be recorded inorder to get > utilization for line syn-0. Am I correct in assuming that all line and > circuit info is required for syn-0 & ethernet. We only report on SYN circuits and DO NOT record anything from ethernet. We poll the following to produce hourly metrics: Circuit COUNTERS hourly Circuit CHARACTERTICS daily Line CHARACTERTICS daily We can then get CIRCUIT STATISTICS (utilization, etc...) for the SYN. Note that your customer does not have to poll the characteristics as often as the counters which could save on disk space. > A customer has been happily recording line and circuit info for sny-0 > every 15 minuites for the last month and now gets the message "Node4 > LOCAL_NS:.decrtr4 Circuit ETHERNET Characteristics not available for > specified time". Is the info he has recorded so far totally useless? I don't understand how the customer could get such an error if requesting SYN statistics. You may want to post the exact command used to produce the error to give more hints. cheers, brad... | |||||
| 5115.12 | More Details | KERNEL::WARDJO | Tue Jan 25 1994 09:27 | 163 | |
Thanks for the reply,
Are you saying that the customer needs to record the line, circuit &
characteristics to get the utilization for syn-0?
The customer is doing the following:-
MCC> sho record node4 decrt4 line * partition *, in domain uk
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:30
Recording parameters for the partition "Identifiers" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:21.20,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "18-JAN-1994 07:35:02.00",
Number of successful polls = 4320,
Time of last failed poll = "11-JAN-1994 15:41:28.69",
Last poll failure reason = "schedule time passed",
Number of failed polls = 6,
Last historical expiration time = "18-JAN-1994 07:35:02.00",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:37
Recording parameters for the partition "Status" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:32.11,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "18-JAN-1994 07:35:31.25",
Number of successful polls = 4317,
Time of last failed poll = "17-JAN-1994 13:51:51.92",
Last poll failure reason = "schedule time passed",
Number of failed polls = 9,
Last historical expiration time = "18-JAN-1994 07:35:31.25",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:39
Recording parameters for the partition "Counters" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:36.03,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "18-JAN-1994 07:36:01.11",
Number of successful polls = 4312,
Time of last failed poll = "17-JAN-1994 14:07:22.42",
Last poll failure reason = "schedule time passed",
Number of failed polls = 13,
Last historical expiration time = "18-JAN-1994 07:36:01.11",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:41
Recording parameters for the partition "Characteristics" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:45.07,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "18-JAN-1994 07:36:31.31",
Number of successful polls = 4313,
Time of last failed poll = "17-JAN-1994 14:08:30.51",
Last poll failure reason = "schedule time passed",
Number of expiration failures = 0
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:43
Recording parameters for the partition "References" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:53.53,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "18-JAN-1994 07:37:02.97",
Number of successful polls = 4313,
Time of last failed poll = "17-JAN-1994 14:07:32.97",
Last poll failure reason = "schedule time passed",
Number of failed polls = 12,
Last historical expiration time = "18-JAN-1994 07:37:02.97",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
Node4 decrt4 Line SYN-0
AT 18-JAN-1994 07:49:45
Recording parameters for the partition "Initial Attributes" :
Recording state = ACTIVE,
State since = 12-OCT-1993 15:59:58.80,
Polling period = 0 00:15:00.00,
Begin time = 30-SEP-1993 15:37:40.78,
End time = 25-MAY-2012 00:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-SEP-1993 15:37:40.78,
Requested by = "MCC_USER",
Time of last successful poll = "NONE",
Number of successful polls = 0,
Time of last failed poll = "18-JAN-1994 07:37:55.52",
Last poll failure reason = "MCC specialized exception
code
:330",
Number of failed polls = 4325,
Last historical expiration time = "NONE",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
MCC> sho node4 decrt4 line syn-0 inbound utilization, for every
0:15:00 -
_MCC> start (17-jan-1994:00:00:00) until 18-jan-1994:00:00:00, in
domain uk
Node4 decrt4 Line syn-0
AT 17-JAN-1994 00:15:00 Statistics
Node4 LOCAL_NS:.decrtr4 Circuit ETHERNET Characteristics not available
for
specified time.
Node4 decrt4 Line syn-0
AT 17-JAN-1994 00:30:00 Statistics
Node4 LOCAL_NS:.decrtr4 Circuit ETHERNET Characteristics not available
for
specified time.
Thanks for your help,
Jon
| |||||
| 5115.13 | more details | CTHQ::WOODCOCK | Skiing's 1st Human Groomer | Tue Jan 25 1994 10:35 | 56 |
Wow, you folks like to poll :). I have never personally tried to get LINE
statistics so I'm not sure it works. Also note you have not specified a
duration in the command. Looking at the command and error below I'd say the
error message is at minimum a bug, it shouldn't give you ethernet errors.
> MCC> sho node4 decrt4 line syn-0 inbound utilization, for every
> 0:15:00 -
> _MCC> start (17-jan-1994:00:00:00) until 18-jan-1994:00:00:00, in
> domain uk
>
> Node4 decrt4 Line syn-0
> AT 17-JAN-1994 00:15:00 Statistics
>
> Node4 LOCAL_NS:.decrtr4 Circuit ETHERNET Characteristics not available
> for
> specified time.
What I can tell you is what actually does work for us.
What we do is record/report on CIRCUIT info and it works quite well. Below you
will find the RECORDs and SHOW STATISTICs command to produce hourly metrics.
Note that it takes a couple of days before reporting is possible because the
CHAR are only polled daily.
record node4 BBZK99 circ SYN-0 part=counters,-
keep age=14 00:00:00, poll period=1:00, in domain .RPT_4
!
spawn wait 0:0:10
record node4 BBZK99 circ SYN-0 part=characteristics,-
keep age=14 00:00:00, in domain .RPT_4
!
spawn wait 0:0:10
record node4 BBZK99 line SYN-0 part=characteristics,-
keep age=14 00:00:00, in domain .RPT_4
!
!
show node4 BBZK99 circuit SYN-0 outb util, inb util,-
count of for cong loss,-
for start yesterday every 1:0 until today -
dur 1:0,in doma .RPT_4, to file=mcc_rpt_tmp:ZKO_PKO.tmp
You will notice we are polling 26 times daily to produce hourly metrics per
circuit. If we wanted 15 minute metrics then we would poll the COUNTERs every
15 minutes but the CHAR still daily. This would work out to be 98 polls per
day per circuit. This is compared to your customers current polling scheme
which is 5 partitions every 15 minutes which is 480 polls daily. I recommend
changing the polling scheme so you save on CPU and DISK space if all you really
need is UTILIZATION and ERROR stats. Also, using the above syntax for circuit
stats is pretty robust.
cheers,
brad...
ps. have your customer set the CIRCUIT COUNTER TIMER to be 65000 seconds on the
router.
| |||||