RFC1317 Sync Table

["Dean D. Throop" <[e-mail]>]

Does anyone have any experience implementing the 
rs232SyncPortTable?  We're finding we can't implement 
rs232SyncPortInterruptedFrames because the interrupt handler for 
the signal dropping doesn't know if the chip actually was in the 
procress of receiving a frame.  Does anyone have any ideas on this?  

We also can't implement rs232InSigChanges or rs232OutSigChanges as 
the total number of modem state changes for many signals because 
the chip handles the modem lines.  For something like switched RTS 
operation there isn't anyway to get the info because the chip did 
it all.  Even if we could get switched RTS operation numbers, this 
information isn't very useful.  It would be more useful to record 
the number of unexpected changes of modem signals.  

Aren't we missing some interesting information on the sync lines?
For example:
	the number of frames send,
	the number of frames received, 
	the number of times DSR didn't come up after raising DTR,
	the number of frames larger than the receive buffer size,
	the number of non-octet aligned frames received,
	the number of times CTS didn't come up after raising RTS, and
	the number of times CTS didn't drop after lower RTS.
	
(I don't believe the LAPB MIB has the number of frames 
transmitted.  It relies on ifInUcastPkts and ifOutUcastPkts which 
are the number of I-frames given to X.25.  I don't know of any 
counters for the raw number of frames sent or received.) 

Dean Throop		[e-mail]