[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2122.0. "Cant get STATISTICS from DECbridge 500" by WOTVAX::HATTOS (I think, Therefore I'm paid less) Thu Jan 16 1992 15:33

    Hi,
    
    I have a problem with getting statistics from our DECBridge 500's
    
    When I ask for statistics information, all goes well, I select network
    utilization or in fact any of the statistics choices, then the
    statistics pop-up 'pops-up' and I get an error message saying "Counter
    Creation Time not Returned"
    
    When I ask for counters from the bridge sure enough the counter
    creation time shows as 'not returned'.
    
    Is this a problem with DECBridge 500 firmware or what?
    
    MCC T1.2.4
    DECBridge V3.0
    
    Thanks for any help,
    Stuart
T.RTitleUserPersonal
Name
DateLines
2122.1Don't know why it is not being returned.TOOK::ANWARUDDINAnwarThu Jan 16 1992 18:402
The action of the Performance Analyzer is correct. No "Counter Creation Time", no statistics.
Hopefully somebody from the LAN or ELMS group can shed light on why it is not being returned.
2122.2DECbridge 500 don't keep reqired countersVIVIAN::MILTONInvisible person it seems!Fri Jan 17 1992 07:028
Stuart,

The decbridge500 doesn't keep byte sent/received counters so utilization can't
be worked out, can they? If you want to look at fddi utilization then I think the 
concentrator is the place to look - I haven't tried that myself cos I can't seem
to register any of the things!

Tony
2122.3documentation/help text problem?CLARID::HOFSTEETake a RISC, buy a VAXFri Jan 17 1992 10:4962

Funny enough I stumbled on the same problem yesterday, when I was trying to
figure out what counters/statistics can be shown for the different bridges.
The first problem is, that the ELMS documentation and the online help
documentation are not in line. The ELMS BPA doc states on page A-2 that
Bytes received (br) and Device bytes send (dbs), are supported on the 
100,150,200,500,600 bridge. It also states on page A-3 a list of calculations,
that has as heading: "Algorithms for bridge line statistics", which seems to
imply that these formulas (and results) are available for ALL bridges.
Than on page A-4 it EXPLICITELY states that Network Utilization applies ONLY
to the 200,500,600 series.

Now the online doc states :

ENTITY

  BRIDGE

    LINE

      STATISTICS



        The following Traffic statistics are available for the BRIDGE LINE
 entity.

                Count of Total Frames Sent
                Count of Total Frames Received
                Originating Bridge Frames
                Terminating Bridge Frames
                Filtered Frames

        The following traffic statistics apply to the LAN200 Bridge only.
                 Network Utilization
                Multicast Utilization
                Single Destination Utilization
                Single Destination Throughput
                Multicast Throughput

        The following Error statistics are available for the BRIDGE LINE entity.

                Bad Frames
                Frames Discarded Lifetime Exceeded
                Frames Received with Unknown Destination Address
                Inbound Frames Lost
                Outbound Frames Lost
                Count of Invalid Protocol Messages
                Error Percent
 
So are the utilization /throughput calculations only available for the LB200
or also for the 500,600?

It would be nice to have some (verified table) like
                100       150       200       500       600
counter_type     X         X      
statistic_type                       X         X         X

Thanks for any clarification

Timo
2122.4Filed as QAR#2158CHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Fri Jan 17 1992 13:2915
The DECbridge 500 should ALWAYS be returning Counter Creation Time (which
is calculated from Seconds Operating). Something is definitely wrong
here if it isn't being returned...

RE: Returning of DECbridge 500 Total Bytes Sent counters:

	1. Only the Ethernet Line can return them (not FDDI side)
	2. Whether they're returned for the Ethernet Line is based
	   on what version of *firmware* the DECbridge is running
	   (hoping to get the version # from LAN BU on this...)

No FDDI statistics are being calculated by the PA FM (i.e. no
statictics for Concentrators).

					Chris Brienen
2122.5no statistics for the lines?CLARID::HOFSTEETake a RISC, buy a VAXMon Jan 20 1992 08:1891
I get the 'Counter Creation Time was not returned.' message on all 15 DECbridge
500 bridges over here. Does that mean that there is definitely something wrong
with ALL these bridges ? 
Do you mean that I cannot get ANY statistics from the lines or only from the
bridge entity itself?

Hereby some output from one of the 15 bridges that I tried.


$ manag/enter
DECmcc (T1.2.4)

MCC> show bridge taafb1 all char

Bridge SSPVBI_NS:.taafb1
AT 20-JAN-1992 11:16:13 Characteristics

Examination of attributes shows:
                          Hardware Type = DEFEB DECbridge 500
                       Firmware Version = V1.6.0
                                     ID = %X08002B1A3865
            LB100 Spanning Tree Version = V0.2.0
          IEEE802 Spanning Tree Version = V0.0.0
                             Port Count = 2
                          Root Priority = 128
                        Bad Hello Limit = 15
               Bad Hello Reset Interval = 5
             Port Test Passed Threshold = 10
                     Port Test Interval = 60 Seconds
                      No Frame Interval = 300 Seconds
                         Hello Interval = 1 Seconds
                            Listen Time = 15 Seconds
                       Forwarding Delay = 30 Seconds
                         Last Load Host = AA-00-04-00-89-36
                  Reset Defaults Switch = False
                          Update Switch = False
                IP Fragmentation Switch = True
                        LB100 Poll Time = 300 Seconds
                 LB100 Response Timeout = 15 Seconds
      LB100 Spanning Tree Compatibility = Auto-Select
                   Device Configuration = ( (
                                   FRU Type = AP Card,
                                  FRU State = Working,
                                     FRU ID = N/A,
                               FRU Revision = Revision 0 ),
                                            (
                                   FRU Type = Single NI Card,
                                  FRU State = Working,
                                     FRU ID = N/A,
                               FRU Revision = Revision 0 ),
                                            (
                                   FRU Type = FI Card,
                                  FRU State = Working,
                                     FRU ID = N/A,
                               FRU Revision = Revision 0 ),
                                            (
                                   FRU Type = QM Card,
                                  FRU State = Working,
                                     FRU ID = N/A,
                               FRU Revision = Revision 0 ),
                                            (
                                   FRU Type = Fan,
                                  FRU State = Working,
                                     FRU ID = N/A,
                               FRU Revision = Revision 0 ) )
                       Software Version = "V2.2"
MCC> show bridge taafb1 line 1 all statis

Bridge SSPVBI_NS:.taafb1 LINE 1
AT 20-JAN-1992 11:18:31 Statistics

Counter Creation Time was not returned.
MCC>
MCC> show bridge taafb1 all count

Bridge SSPVBI_NS:.taafb1
AT 20-JAN-1992 11:17:56 Counters

Examination of attributes shows:
                     Device Frames Lost = 2 Frames
                  Counter Creation Time = 12-SEP-1991 13:58:44.39
                      Seconds Operating = 11222352 Seconds
                      Management Resets = 0
                               Powerups = 20
             Spanning Tree Mode Changes = 18
                     Unsolicited Resets = 0
                      Invalid Passwords = 0
MCC>


2122.6QUIVER::CHILDSEd ChildsMon Jan 20 1992 13:0614
    Here's what I've discovered:

    * If you have not augmented your dictionary with
    MCC_BRIDGE_LINE_STATISTICS.COM then Counter Creation Time is returned
    on the ethernet side of DECbridge 500s.

    * When you augment your dictionary with the PA stuff (which the ELM
    T1.2.4 kit does) Counter Creation Time is no longer returned.

    * Counter Creation Time is not returned by the bridge itself, but is a
    synthesized attribute (the Bridge AM generates it from the Seconds
    Operating counter).

    I'm looking into this now and I'll keep you all posted.
2122.7QUIVER::CHILDSEd ChildsTue Jan 21 1992 16:059
| If you have not augmented your dictionary with
| MCC_BRIDGE_LINE_STATISTICS.COM then Counter Creation Time is returned
| on the ethernet side of DECbridge 500s.

    This isn't true -- I must have goofed when I was trying out things!

    This is a problem with the Bridge AM code.  The ELM field test update
    kit will have this fixed.