[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

5484.0. "Report Packet error" by GLDOA::KATZ (Follow your conscience) Fri Aug 13 1993 13:47

    This morning I had a problem with the TCP/IP SNMP Error Summary Report.
    I ran the report for a 24 hour period for the 10 hosts with the highest
    error count. Eight of my routers came back fine but  two of my 
    Cisco routers outgoing packets came back like this:
    
    host name .ip.frmosb
    Number of interfaces 	5
    
    
    		Total Packets 	Total 		Total Error
    				Error Packets	Packet percent
    In            2453226               5	0.00
    Out		115301789 	232565103	*****
    Total	117755015	113838514	96.67
    
    
    Successful Polls:	33 out of 44 total polls
    
    What do the asterisks mean and why did I get an erroneous
    total packet count for the outgoing? Thanks.
    
    			-Jim-
T.RTitleUserPersonal
Name
DateLines
5484.1DTR field overflowMLNCSC::BARILAROFri Aug 20 1993 06:1621
    Hi Jim,
    
    	The asterisks means an overflow of the display fields in
    	Datatrieve, that's used to write the standard MCC report
    	procedures.
    
    	In this case you got them because for this router you've
    	232565103 pckts/error .vs. 115301789 that's means more than
    	200% of error rate, and the field "Total Error Packet percent"
    	on Datatrieve is defined with the mask PIC Z9.99 (2 digit
    	before the decimal point and 2 after). 
    
    	So, the real problem  aren't the asterisks, but why you've
    	more packets in error that the packets trasmitted , that if
    	I remember well should be the total of packets (the ones 
    	trasmitted with success and the ones in error), so it be 
    	impossible.
    	Should be an error on the procedure, or on the Dbase or....
    
    				Sorry to not have the solution,
    				Ciao 	Luciano