List of TelePAC faults (Position as of 12 Sept 86) 1.2 Points addressed with Mr Gilmour regarding JNT Spec (Telefile) Guaranteed PSS compatibility (BG 1) SEEL letter of 12 02 86 Call statistics in Clear packet (BG 2) Ok, but see N7 Call redirection (BG 3) Ok Load Sharing (BG 4) Ok, but see N6 Performance monitor (BG 6) Ok Fault warning (BG 7) Ok (but could be more) Network management (BG 8) Ok, but multiple PSE not tried Various packet counts (BG 9) Clear,Int,Rst SENT not counted Displayable DTE addresses (BG 11) No (not by address yet) Password on BASE: (BG 12) Ok MTBF (BG 13) Ok (SEEL letter of 12 02 86) Crash on buffer exhaustion (BG 14) Ok Hold link down (BG 15) Ok Change of line speeds (BG 16) Ok 1.3 Gilmore/Cheney-reported bugs not dealt with above (Telefile) Reset code of 0/0 on errors (BG 3) Ok Clear code of 0/0 on link down (BG 4) Now get 9/0 (want 9/43) Packet size of 256 (BG 13, CJC 3) No (see Q5) No response to REJ command (CJC 1) No Spurious pairs of Clears (CJC 2) Ok but see Q9 Crash because of incorrect configuration (CJC 4) Ok - but see N3 Delays on response to Call Request (BG 9, CJC 5a, 13) Ok Wrong LCN used after Clear to Call Request (CJC 5b) Ok Clear held up until after Accept (CJC 6b) No, see Q7 Reset is not propagated (CJC 7) Ok but see Q1 and Q2 1.4 Gilmore/Cheney-reported deficiences not dealt with above Session statistics from call setup (BG 2) Ok Unmatched called addresses (BG 5, CJC 12) Ok, circumvention, but see S11 No response to illegal LCGN (BG 6) Ok (X.25 protocol spec), but message would be helpful DTE sends network clearing codes (BG 7) Ok (on-off by NET option) Display of link output queue size (BG 8) No? Change number of LCNs should not require reboot (BG 10) No Documentation (BG 11, CJC 22) No (partial attempt not successful) Respond Clear Conf. to Clear after Call Req. (CJC 6a) Ok *check* Need multiple LCGs (CJC 9) No Supervisory command recovery after REJ (CJC 10) Not tested Lower and upper case (CJC 11a) No DEL (CJC 11b) No Non-immediate configuration (CJC 15) No Selection of address table entries (CJC 16) No Configuration of address table (CJC 17) No DTE/DCE instead of A/B (CJC 19) No Physical DCE presentation (CJC 20) No X.25 subscription options (CJC 21) No Addresses in billing records are zero-filled (CJC 8) No Cambridge faults - version 0664 Q1 RESET REQUEST response to RESET CONF. Q2 Packet sequence number not zero after reset. Q3 Delay between receiving DISC and sending SABM. Q4 SARM sent after receiving second DISC. Q5 Incorrect packet size negotiation. Q6 No PSS-style extended-format CLEAR or CLEAR CONF. Q7 CLEAR not forwarded to non-accepting host. Q8 Repeated call attempts. Q9 Wrong state after failed call attempts. Q10 Missed acknowlegment after CLEAR CONF. Q11 Monitor not stable to unaasigned interrupts. S1 Upper/lower case. S2 DEL. S3 Interpretation of input line. S4 Use PAD parameters in VCP. S5 Allow type-ahead. S6 VCP output overwrites input because of lack of CRLF. S7 Need restarted log message. S8 Configure discs in other than aborted state. S9 Nonzero diagnostic codes needed. S10 COPY ALL for physical links. S11 Catch-all resource should clear 0D not 09. S12 DIL switch for clock speed on EIA cards. S13 Jumpers for DTE clock at TTL levels. S14 Blanking plates. ERCC Reported Faults N1 When a call is 'timed out', the TelePAC repeats the call attempt 5 times. It should not repeat the call attempt. N2 When a 'simple' error occurs on a line, eg an incorrect L2 address is seen, the TelePAC is too quick in disconnecting the link (PSS will ignore a frame with an incorrect address) It appears that when line faults are occuring, some bad packets can get through the CRC check & this causes then provokes the TelePAC to disconnect the link. *** CRC problem fixed by a mod to the V24 board - July 86 N3 Configuration. If a large number of Billing records are asked for (but less than the stated max), the TelePAC crashes on BOOT & it can be very difficult to stop it looping in the diagnostics. N4 After the above, the only way of restoring the TelePAC is to reset the memory, it is NOT enough to simply reset the number of billing records and re-boot N5 Buffers dropped from almost 400 to 173 for no apparent reason. The number stayed that from 5pm to 1pm the next day. It then rose again to 260, again for no apparent reason. N6 Load Sharing. When a load shared line has gone down and up, calls do not appear to then use that line. N7 PSS Statistics. Only operate one way round. N8 When a line attached to a line driver goes down, the switch puts out a constant stream of meesages in the form "Input too long". This is thought to be caused by the switch not searching for a flag packet after the 1st error. N9 Whan a call is nogotiated with a packet size of 128 and a packet > 128 is sent to the Telepac, a) it is not reset and b) the oversize packet is sent to the receiving host. (version 0451) N10 When a call is made to a line which is up, but the host then makes no response (ie, really is down), then after the timeout period, the call is cleared with the code 00/00. N11 On a busy line, ie with approx 64 calls in progress, a single call or several of them can stick. The effect is that the call accept packet is sent back to the originator of the call but there is disagrement between the two channels on the TelePAC as to the state of data which has been transmitted by the called address but not transmitted to the caller. Evidence was sent to Telefile. N12 A DELE of the stats of a line does not properly clear the numbe rof packets received & transmitted and leaves the numbers output by the commands STAT and POLL different. N13 When a Call Accept is sent to the TelePAC negotiating a window size of zero, the TelePAC 'accepts' it rather than sending a RESET 05/C6 N14 When a Call is made to a line in the state 'FRMR', the call is rejected by the TelePAC after a short delay with the code 00/00 rather than 09/00 N15 When a line is disconnected, a line can go into the FRMR state and remain 'for ever' in that state. N16 On release 664, when a call is made with packet size 128/128, no RESET is generated if a packet of > 128 is then used. N17 When the TelePAC is powered on, a line can fail to start properly, ie with correct timing present, the TelePAC does not transmit flags etc. N18 Call setup is too slow N19 Two concatenated packets were output by the Telepac, the packet, 209 bytes in length had a correct checksum and the entire header of the 'second' packet was present. The next packet transmitted had a transmit sequence count of 3. N20 (The original N10) When a call is made to an address not set-up in the TelePAC, it is routed to an internal service and there is a delay until the call is cleared. N21 The current number of calls on a link can be grossly wrong, an example where > 500 calls were seen on a link was sent to Telefile. N22 A restart packet from the TelePAC contains a 'DTE originated' cause field (from a DCE). Additional faults 1 T1 times is unstable, can be extremely short at times 2 When a REJ is sent with a final bit set in response to a block with a poll bit sent by the TelePAC, the TelePAC will FRMR.