| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4969.1 | Looks like a PA bug | QUIVER::HAROKOPUS | | Thu Apr 29 1993 12:43 | 10 |
| I've noticed this myself. It looks like the counters are ok
but the PA FM is using the wrong formula for network utilization.
Mike Dransfield did some experimentation with this and it looks like
the network utilization is only tracking bytes sent instead of
both bytes sent and bytes received.
I have reported this problem to the PA developers.
-Bob
|
| 4969.2 | Just verified the PA equations .. | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Thu Apr 29 1993 17:07 | 28 |
| Network Utilization:
100 * ( bytes_sent + bytes_received ) * 8
-----------------------------------------
time
--------
speed
Single Destination Utilization:
100 * ((bytes_rec - mcast_bytes_rec) + (bytes_sent - mcast_bytes_sent)) * 8
---------------------------------------------------------------------------
time
--------
speed
Seems right to me .. I don't know why you're seeing bad data.
Could you record bridge counters, then calcualte the stats based on
the historical counters .. and post both the counters and stats? Then
I can double check everything by hand, using the exact counter data that
PA is using.
/keith
|
| 4969.3 | Historian problems | BRAT::BUKOWSKI | | Fri Apr 30 1993 11:50 | 37 |
| I am trying, but here I am not able to get data from back from my MIR.
I haven't used the historian before, so I may be missing something.
Do you see what is wrong here?
Mike
Bridge DEC:.MKO.BR.MKO1H1BRH101 LINE 2
AT 30-APR-1993 10:48:02
Recording parameters for the partition "Counters" :
Recording state = ACTIVE,
State since = 30-APR-1993 10:04:37.27,
Polling period = 0 00:01:00.00,
Begin time = 30-APR-1993 10:05:00.00,
End time = 30-APR-1993 11:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-APR-1993 10:04:23.07,
Requested by = "LATMGR",
Time of last successful poll = "30-APR-1993 10:48:00.84",
Number of successful polls = 44,
Time of last failed poll = "NONE",
Last poll failure reason = "N/A",
Number of failed polls = 0,
Last historical expiration time = "30-APR-1993 10:48:00.84",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
SHOW bridge .mko.br.mko1h1brh101 line 2 ALL COUNT, FOR START =
(30-APR-1993:10:05:00.00)
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 10:47:24 Counters
Requested data not available for specified time
|
| 4969.4 | in domain=jjj | CTHQ::WOODCOCK | | Fri Apr 30 1993 14:10 | 11 |
| Hi Mike,
You need to tell it what domain...
SHOW bridge .mko.br.mko1h1brh101 line 2 ALL COUNT, FOR START =
30-APR-1993:10:05 dur 6:0, IN DOMAIN .mko.domain.mko
regards,
brad...
|
| 4969.5 | Can't get data from Historian | BRAT::BUKOWSKI | | Fri Apr 30 1993 15:22 | 53 |
| Ok.
Now a new problem. I added the ,IN DOMAIN .MKO.DOMAIN.MKO to my
command line, but it is now only showing me the counters for the latest
poll.. The show recording command shows that multiple polls have been
successfull and there have been no failures. What happened to all my
data?
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 14:19:42
Recording parameters for the partition "Counters" :
Recording state = ACTIVE,
State since = 30-APR-1993 14:02:57.70,
Polling period = 0 00:01:00.00,
Begin time = 30-APR-1993 14:05:00.00,
End time = 30-APR-1993 19:00:00.00,
Keep age = 45 00:00:00.00,
Request time = 30-APR-1993 13:34:30.57,
Requested by = "LATMGR",
Time of last successful poll = "30-APR-1993 14:19:00.22",
Number of successful polls = 15,
Time of last failed poll = "NONE",
Last poll failure reason = "N/A",
Number of failed polls = 0,
Last historical expiration time = "30-APR-1993 14:19:00.22",
Time of last expiration failure = "NONE",
Last expiration failure reason = "N/A",
Number of expiration failures = 0
MCC>
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 14:19:00 Counters
Examination of attributes shows:
Counter Creation Time = 13-MAR-1993 15:51:28.22
Port Restarts = 0
Total Frames Received = 3228676227 Frames
Total Bytes Received = 748324180948 Bytes
Device Frames Received = 1657 Frames
Device Bytes Received = 106402 Bytes
Multicast Frames Received = 25779826 Frames
Multicast Bytes Received = 6546313816 Bytes
Total Frames Sent = 2977284774 Frames
Total Bytes Sent = 631499403649 Bytes
Device Frames Sent = 4198490 Frames
Device Bytes Sent = 271367802 Bytes
.
.
.
Help.....
|
| 4969.6 | exit | BRAT::BUKOWSKI | | Fri Apr 30 1993 15:25 | 19 |
| In the last reply forgot to list the command I used to show the
counters .. here it is ..
SHOW bridge .mko.br.mko1h1brh101 line 2 all count, for START 14:08, in
domain .mko.domain.mko, to file tmp.dat
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 14:19:00 Counters
Examination of attributes shows:
Counter Creation Time = 13-MAR-1993 15:51:28.22
Port Restarts = 0
Total Frames Received = 3228676227 Frames
Total Bytes Received = 748324180948 Bytes
Device Frames Received = 1657 Frames
Device Bytes Received = 106402 Bytes
Multicast Frames Received = 25779826 Frames
Multicast Bytes Received = 6546313816 Bytes
|
| 4969.7 | | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Fri Apr 30 1993 16:31 | 15 |
| >> SHOW bridge .mko.br.mko1h1brh101 line 2 all count, for START 14:08, in
>> domain .mko.domain.mko, to file tmp.dat
In the 'For Time' syntax I think you have to give a duration of how
much data you are interesting in .. so you might say:
for start 14:08:00 duration 00:30:00
to say you are interested in data beginning at 14:08:00 to 14:38:00
/keith
btw: I've been trying to record and process bridge counters all day
and can't figure it out either 8( but if both of us are trying maybe
we'll get some data recorded and displayed
|
| 4969.8 | Some data... | BRAT::BUKOWSKI | | Fri Apr 30 1993 17:46 | 161 |
| Hi,
We are making some progress, but I still can't get the information
from the time I request..
Mike
SHOW bridge .mko.br.mko1h1brh101 line 2 all count, for START 14:08 duration
00:01, in domain .mko.domain.mko
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 15:07:00 Counters
Examination of attributes shows:
Counter Creation Time = 13-MAR-1993 15:51:28.25
Port Restarts = 0
Total Frames Received = 3231731267 Frames
Total Bytes Received = 748780690723 Bytes
Device Frames Received = 1850 Frames
Device Bytes Received = 118754 Bytes
Multicast Frames Received = 25798506 Frames
Multicast Bytes Received = 6552424950 Bytes
Total Frames Sent = 2980045893 Frames
Total Bytes Sent = 632025027119 Bytes
Device Frames Sent = 4201603 Frames
Device Bytes Sent = 271726353 Bytes
Multicast Frames Sent = 650525200 Frames
Multicast Bytes Sent = 88078455116 Bytes
Bad Frames Received = 180 Frames
Transmit Frames Lost = 519 Frames
Lifetime Exceeded Frames = 0 Frames
Receive Frames Lost = 0 Frames
Frames Filtered = 912582903 Frames
Bytes Filtered = 173229808977 Bytes
Receive Overruns = 0 Frames
Forwarding State Entered = 1
Invalid Device Messages = 0 Frames
Bad Hellos Limit Exceeded = 0
Multicast Frames Filtered = 0 Frames
Multicast Device Frames Received = 1850 Frames
Multicast Device Frames Sent = 4201603 Frames
Device Frames Lost = 0 Frames
Transmit Error Frames = 1 Frames
Bad Bytes Received = 35988 Bytes
Multicast Source Frames Received = 0 Frames
Transmit Error Bytes = 64948 Bytes
Invalid Device Bytes = 0 Bytes
Multicast Device Bytes Received = 118754 Bytes
Multicast Device Bytes Sent = 271726353 Bytes
Oversize Frames = 1 Frames
Framing Errors = 87
Transmit Multiple Collisions = 152667003
Carrier Lost = 0
Collision Limit Exceeded = 0
Unknown Destination Addresses Received = 132159
Frames Addressed Filtered = 912582903 Frames
Bytes Addressed Filtered = 0 Bytes
Bytes Protocol Filtered = 0 Bytes
Collision Presence Test Failed = 0
Length Error = 0
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 15:08:00 Counters
Examination of attributes shows:
Counter Creation Time = 13-MAR-1993 15:51:28.24
Port Restarts = 0
Total Frames Received = 3231802399 Frames
Total Bytes Received = 748791223233 Bytes
Device Frames Received = 1853 Frames
Device Bytes Received = 118946 Bytes
Multicast Frames Received = 25798950 Frames
Multicast Bytes Received = 6552556611 Bytes
Total Frames Sent = 2980107265 Frames
Total Bytes Sent = 632035761966 Bytes
Device Frames Sent = 4201666 Frames
Device Bytes Sent = 271733044 Bytes
Multicast Frames Sent = 650534422 Frames
Multicast Bytes Sent = 88079726631 Bytes
Bad Frames Received = 180 Frames
Transmit Frames Lost = 519 Frames
Lifetime Exceeded Frames = 0 Frames
Receive Frames Lost = 0 Frames
Frames Filtered = 912605604 Frames
Bytes Filtered = 173232398169 Bytes
Receive Overruns = 0 Frames
Forwarding State Entered = 1
Invalid Device Messages = 0 Frames
Bad Hellos Limit Exceeded = 0
Multicast Frames Filtered = 0 Frames
Multicast Device Frames Received = 1853 Frames
Multicast Device Frames Sent = 4201666 Frames
Device Frames Lost = 0 Frames
Transmit Error Frames = 1 Frames
Bad Bytes Received = 35988 Bytes
Multicast Source Frames Received = 0 Frames
Transmit Error Bytes = 64948 Bytes
Invalid Device Bytes = 0 Bytes
Multicast Device Bytes Received = 118946 Bytes
Multicast Device Bytes Sent = 271733044 Bytes
Oversize Frames = 1 Frames
Framing Errors = 87
Transmit Multiple Collisions = 152669572
Carrier Lost = 0
Collision Limit Exceeded = 0
Unknown Destination Addresses Received = 132159
Frames Addressed Filtered = 912605604 Frames
Bytes Addressed Filtered = 0 Bytes
Bytes Protocol Filtered = 0 Bytes
Collision Presence Test Failed = 0
Length Error = 0
Bridge DEC:.mko.br.mko1h1brh101 LINE 2
AT 30-APR-1993 15:09:00 Counters
Examination of attributes shows:
Counter Creation Time = 13-MAR-1993 15:51:28.21
Port Restarts = 0
Total Frames Received = 3231870799 Frames
Total Bytes Received = 748802110609 Bytes
Device Frames Received = 1857 Frames
Device Bytes Received = 119202 Bytes
Multicast Frames Received = 25799269 Frames
Multicast Bytes Received = 6552678454 Bytes
Total Frames Sent = 2980164210 Frames
Total Bytes Sent = 632045838661 Bytes
Device Frames Sent = 4201730 Frames
Device Bytes Sent = 271740422 Bytes
Multicast Frames Sent = 650543634 Frames
Multicast Bytes Sent = 88080969870 Bytes
Bad Frames Received = 180 Frames
Transmit Frames Lost = 519 Frames
Lifetime Exceeded Frames = 0 Frames
Receive Frames Lost = 0 Frames
Frames Filtered = 912627982 Frames
Bytes Filtered = 173235241857 Bytes
Receive Overruns = 0 Frames
Forwarding State Entered = 1
Invalid Device Messages = 0 Frames
Bad Hellos Limit Exceeded = 0
Multicast Frames Filtered = 0 Frames
Multicast Device Frames Received = 1857 Frames
Multicast Device Frames Sent = 4201730 Frames
Device Frames Lost = 0 Frames
Transmit Error Frames = 1 Frames
Bad Bytes Received = 35988 Bytes
Multicast Source Frames Received = 0 Frames
Transmit Error Bytes = 64948 Bytes
Invalid Device Bytes = 0 Bytes
Multicast Device Bytes Received = 119202 Bytes
Multicast Device Bytes Sent = 271740422 Bytes
Oversize Frames = 1 Frames
Framing Errors = 87
Transmit Multiple Collisions = 152672146
Carrier Lost = 0
Collision Limit Exceeded = 0
Unknown Destination Addresses Received = 132159
Frames Addressed Filtered = 912627982 Frames
Bytes Addressed Filtered = 0 Bytes
Bytes Protocol Filtered = 0 Bytes
Collision Presence Test Failed = 0
Length Error = 0
|
| 4969.9 | I found a bug in PA for Bridge Statistics: | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue May 04 1993 14:20 | 15 |
| I found the bug in PA which was causing bad statistics for:
o Bridge Network Utilization
o Bridge Multicast Utilization
The bug was causing PA to loose the 'Total Bytes Sent' in Network Utilization
and 'Multicast Bytes Sent' in Multicast Utiliation.
I tested the fix with Recorded Bridge-620 counters and hand calculations.
I don't know if this fix can get into the v1.3 MUP .. or will have to wait
till the next release. I'll check to see if I can make an EXE with the fix
available to Internal Sites.
/keith
|
| 4969.10 | | ABACUS::BUKOWSKI | | Tue May 04 1993 17:15 | 15 |
| Two questions:
1- Does this bug just effect the Bridge line characteristics or does it
effect all entities capable of utilization?
2- If this doesn't make the 1.3 MUP, will there be a patch available?
ok 3 questions.
3- Do you know when the MUP is due?
Thanks,
Mike
PS: I finally got the recording to work. I had my MCC_TDF logical
still set to the winter time (-5:00).
|
| 4969.11 | No date for the MUP at the moment | TOOK::MINTZ | Erik Pavlik Mintz | Tue May 04 1993 17:19 | 9 |
| As indicated in the original discussion of "the MUP", the primary
purpose of that release will be to correct a DECthreads packaging issue,
as required by VMS/SDT engineering.
Unfortunately, VMS/SDT engineering has not given us a date for when
they will be ready with their part of the packaging solution, and as
a result, we can not provide a date for when our update will be released.
-- Erik
|
| 4969.12 | Three answers | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue May 04 1993 17:37 | 41 |
|
RE: .10
> 1- Does this bug just effect the Bridge line characteristics or does it
> effect all entities capable of utilization?
I searched all the PA statistical equations and only found the problem
on the two attributes I mentioned:
o Network Utilization
o Multicast Utilization
The Single 'Single Destination Utilization' appeared Ok, but I think
I'll double check the equations by hand just to be sure.
>
> 2- If this doesn't make the 1.3 MUP, will there be a patch available?
We don't do patches any more .. so an entire new EXE would be provided.
For Digital Internal-use-only, I can't see why making the new EXE available
would be a problem .. Handing it out to customers is fine in my opinion too;
This is probably handled at a higher level.
> ok 3 questions.
>
> 3- Do you know when the MUP is due?
No idea
>
> Thanks,
> Mike
> PS: I finally got the recording to work. I had my MCC_TDF logical
> still set to the winter time (-5:00).
That'll do it to you! I had a lot of problems too .. I finally deleted
the MIR files that get created in your login directory and started all over
again .. it worked fine then.
/keith
|
| 4969.13 | | TOOK::PELAGATTI | Anne | Wed May 12 1993 14:29 | 11 |
| Just a point of clarification ....
As Keith points out, patches are not done anymore. Entire images
are provided. If this change does not make it into the MUP, then
we can provide the image for internal use only. We can also
provide the image to Colorado support so that customers can be
given the fixes.
Due to the support nightmare, neither we, nor the field should provide
images to customer except through Colorado.
|
| 4969.14 | where is the fix for Bridge Sataistics ? | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Mon Feb 07 1994 23:05 | 16 |
|
A customer has experience this problem with bridge statistics mension
in the base note - incorrect network utilization figures. Does anyone know
where the mup,patch or fixkit is ? I have applied MCCECO01013 kit which
contains MCC_PA_FM.EXE ident "DECMCC V1.3B-02" link date "30-AUG-1993".
but the problem remains the same.
The release notes for MCCECO01013 does not say anything about the fix
yet .11, .12 and .13 implied that a MUP exist .
Someone please tell me where to get the proper fix ? or if it exists ?
Andrew
|
| 4969.15 | Please escalate! | BIKINI::KRAUSE | European NewProductEngineer for MCC | Thu Feb 10 1994 04:30 | 14 |
| There is a MCC_PA_FM.EXE that fixes the bridge statistics problem.
Unfortunately it does NOT contain other fixes. In other words: only one
problem fiexed per installation. There are numerous CLDs hanging around
requesting a PA with all fixes in it, but...
I hesitate to make the PA fix public, because there is no way to keep
track of who has which version of the module. They all (four) have
identical names and almost identical link IDs (only the minute is
different) and I don't want to create a support nightmare.
Please escalate the problem formally (through CLD) to create more
management attention. The squeeky wheel gets the oil...
*Robert
|