[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

3272.0. "VBAM Counters vs. Console Counters" by ODIXIE::PEACOCKR () Tue Jun 30 1992 13:39

    I have just installed the VBAM Access Module at a customer site and
    after looking at the counters and such, have a few questions (forgive
    the obvious ones - I have been unable to obtain the VBAM AM
    documentation):
    
    1.	The customer was interested in looking for CRC errors on the
    Vitalink.  From the console terminal on the Translan 350 we could see a
    counter for CRC errors.  However, from the VBAM AM there was no such
    counter.  Is there a VBAM counter that corresponds to the CRC error
    count he sees on the console?  (I was expecting counters to be a one to
    one correlation)
    
    2.	What are FCS errors?  
    
    3.	Is it possible to reset the counters from the VBAM AM?
    
    4.	Does the Reset command do this or does it reboot the Translan?
    
    
    Thanks for any help you can provide.  We're having difficulty getting
    the documentation out here.
    
    Rick
T.RTitleUserPersonal
Name
DateLines
3272.1TOOK::MCPHERSONLife is hard. Play short.Tue Jun 30 1992 16:5131
    
>    1.	The customer was interested in looking for CRC errors on the
>    Vitalink.  From the console terminal on the Translan 350 we could see a
>    counter for CRC errors.  However, from the VBAM AM there was no such
>    counter.  Is there a VBAM counter that corresponds to the CRC error
>    count he sees on the console?  (I was expecting counters to be a one to
>    one correlation)

CRC errors are in the COUNTER attribute partition for the LINE subentity.
	e.g. MCC> SHOW TRANSLAN .FOO LINE * ALL COUNT
    
>
>    2.	What are FCS errors?  
>    

FCS :== Frame Check Sequence


>
>    3.	Is it possible to reset the counters from the VBAM AM?
>    

Only by rebooting the bridge. (same behavior as DEC BRIDGE)
>
>    4.	Does the Reset command do this or does it reboot the Translan?
>
     MCC> RESET TRANSLAN .FOO DEFAULTS = TRUE    
    
	will reboot the Translan (and consequently reset the counters...)

/doug
3272.3Strange.MCDOUG::MCPHERSONLife is hard. Play short.Tue Jun 30 1992 21:0424
>    I am curious as to why CRC errors still do not show up from the Iconic
>    Interface.  We did a show counters of all of his Vitilinks and on each
>    line that was configured to operate and it nevered showed a CRC counter
>    anywhere.

    Well, I'm curious too, Rick.  You say it shows up in FCL but NOT the Iconic
    Map????
    	- What version of software are you running on the TransLANs? 
    	- What variant of TransLANs are you using?  III, 350, 320, 335?
    	- Can you post a snapshot of the SHOW Commands you used?  
    	- Can you post the output of a SHOW LINE * ALL CHAR, too?

    The only thing I can think of offhand is if we may be seeing some weird
    behavior about handling of the LINE variants...

    CRC Errors is a Counter Attribute for the LINE subentity, but ONLY for
    LINEs that return "Link Type = Vitalink Serial".  (i.e. there's a DEPENDS
    ON clause in the MSL).

    If the "Link Type" attribute of the lines you're looking at are NOT
    "Vitalink Serial" (i.e. you're looking at Ethernet Ports) then you will NOT
    see the CRC Errors Counter returned.
 
    /doug
3272.4More on Counters - I'm confused!ODIXIE::PEACOCKRTue Jun 30 1992 21:1573
       I just dialed in to a customer site to try it from the command line.
       This is a Vitalink Translan 350.  I tried the command on both line 1
       and line 2 (which, as far as I know are being used).  Here's what I
       got:
    
     MCC> show translan atlanta_dome line 1 all counters
    
        TRANSLAN DSP_NS:.atlanta_dome LINE 1
        AT 30-JUN-1992 17:06:40 Counters
    
        Examination of attributes shows:
                          Counter Creation Time = 28-JUN-1992 13:59:42.24
                               Tx Buffer Errors = 0
                        Enet Tx Underrun Errors = 0
                                Late Collisions = 0
                             Carrier Loss Error = 0
                               Retry Errors = 0
                           Rx Buffer Errors = 0
                          Rx Overrun Errors = 0
                           Receive Overruns = 0 Frames
                                 FCS Errors = 1
                          Controller Resets = 0
                         Frames Transmitted = 6436461 Frames
                  Transmit Frames Discard = 0 Frames
                 Discards Protected Network = 0 Frames
                          Bytes Transmitted = 431706512 Bytes
                      One Retry To Tx Frame = 18529
                        More Retry Tx Frame = 29817
                       Early Discards on Rx = 24114450 Frames
                            Frames Received = 8435350 Frames
                Known Single Destination Rx = 7746394 Frames
              Unknown Destination Frames Rx = 742 Frames
                        Multicast Frames Rx = 688202 Frames
                         Late Discard On TX = 371384 Frames
                             Bytes Received = 898211928 Bytes
                    Forwarding Change Count = 0
                  Bad Hellos Exceeded Count = 0
    
    TRANSLAN DSP_NS:.atlanta_dome LINE 2
    AT 30-JUN-1992 17:17:16 Counters
    
    Examination of attributes shows:
                      Counter Creation Time = 28-JUN-1992 13:59:42.50
                                 CTS Errors = 0
                                 DCD Errors = 0
                               Abort Errors = 0
                                 CRC Errors = 116 Frames
                     SIO Tx Underrun Errors = 0
                           Receive Overruns = 0 Frames
                         Frames Transmitted = 5427860 Frames
                  Transmit Frames Discarded = 542670 Frames
                 Discards Protected Network = 0 Frames
                           Frame Congestion = 0
                            Byte Congestion = 0
                          Bytes Transmitted = 549820031 Bytes
                            Frames Received = 3293681 Frames
                Known Single Destination Rx = 3112800 Frames
              Unknown Destination Frames Rx = 0 Frames
                        Multicast Frames Rx = 180876 Frames
                         Late Discard On TX = 175881 Frames
                             Bytes Received = 204064997 Bytes
                    Forwarding Change Count = 0
                  Bad Hellos Exceeded Count = 0
    
    
    Why are the counters so different?  I have several on Line 2, including
    the CRC errors, which didn't show up on line 1.  Is there something
    different in the configuraton of the lines that would make them so
    different?
    
    Thanks,
    
    Rick
3272.5Better Learning through Notes!ODIXIE::PEACOCKRTue Jun 30 1992 21:2421
    I think I may have figured out my mistake.
    
    In looking at the characteristics of the lines, line 1 shows
     
    		Link Type = IEEE 802.3 CSMA/CD
    
Line 2 shows:
    
    Examination of attributes shows:
                            Link Type = Vitalink Serial
                            Link Activation = True
      
    
    From looking at the rest of the lines, it would appear that only active
    lines that have been configured for Vitalink Serial show the CRC
    counters.
    
    Is this correct?
    
    Rick,
    
3272.6case closed!TOOK::MCPHERSONLife is hard. Play short.Wed Jul 01 1992 01:5416
>    
>    From looking at the rest of the lines, it would appear that only active
>    lines that have been configured for Vitalink Serial show the CRC
>    counters.
>    
>    Is this correct?
>    

Yep. Give that man a raise.

If you skip to the bottom of my (probably overly long) reply in .3 you'll see
that only the Vitalink *SERIAL* lines return the CRC Errors counter; the
Ethernet ports don't.

.doug