[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
864.0. "FDDI FXA fatal error count" by USHS01::LIN (Terry Lin) Tue Feb 16 1993 21:18
One of my customer just got their 7610 in last week. They seem to
have problem with VMS backup from disk to disk served by 7610. The
backup process was in RWSCS state a lot. Someone suggested that might
be a faulty lan adapter. 7610 comes with both FDDI and ethernet
controller. We got a chance to show lan/error on the 7610 and here is
the result: Is FXA Fatal error count 26 normal? Thanks.
VAX/VMS System analyzer
-- FXA Error Information 16-FEB-1993 18:10:26 --
Receive failures 0 Send failures
0
Unrec frame dest 0 Xmt coll chk failure
0
Data overrun 0 Transmit timeouts
0
System buff unavail 0 Excessive collisions
0
User buff unavail 0 Last exc collision
0
Frames lost, hw buff 0 No work transmits
0
Invalid length 0 Bad PTE transmits
0
58Invalid length (2 sh) 0
Fatal error count 26 RDL errors
0
Transmit timeouts 0 Last fatal error 16-FEB
18:08:36
Restart failures 0 Prev fatal error 16-FEB
18:03:23
Power failures 0 Last error CSR
00000000
Hardware errors 0 Fatal error code
00000003-XmtTimeout
Control timeouts 0 Prev fatal error
00000003-XmtTimeout
-- FXA1 60-07 (SCA) Counters Information 16-FEB-1993 18:10:26 --
LasTransmit timeouts 0 Last fatal error 16-FEB
18:08:36
Restart failures 0 Prev fatal error 16-FEB
18:03:23
Power failures 0 Last error CSR
00000000
Hardware errors 0 Fatal error code
00000003-XmtTimeout
Control timeouts 0 Prev fatal error
00000003-XmtTimeout
-- FXA1 60-07 (SCA) Counters Information 16-FEB-1993 18:10:26 --
Last receive None Last transmit
None
Octets received 0 Octets sent
0
PDUs received 0 PDUs sent
0
Mcast octets received 0 Mcast octets sent
0
Mcast PDUs received 0 Mcast PDUs sent
0
Unavail user buffer 0 Last start attempt 16-FEB
18:08:37
Last start done 16-FEB 18:08:51 Last start failed
None
-- FXA2 60-03 (DECNET) Counters Information 16-FEB-1993 18:10:26
--
Last receive None Last transmit 16-FEB
18:10:25
Octets received 0 Octets sent
0
PDUs received 0 PDUs sent
501
Mcast octets received 0 Mcast octets sent
0
Mcast PDUs received 0 Mcast PDUs sent
0
Unavail user buffer 0 Last start attempt
None
Last start done 16-FEB 18:10:25 Last start failed
None
-- FXA3 60-04 (LAT) Counters Information 16-FEB-1993 18:10:26 --
Last receive None Last transmit
None
Octets received 0 Octets sent
0
PDUs received 0 PDUs sent
0
McasLast receive None Last transmit
None
Octets received 0 Octets sent
0
PDUs received 0 PDUs sent
0
Mcast octets received 0 Mcast octets sent
0
Mcast PDUs received 0 Mcast PDUs sent
0
Unavail user buffer 0 Last start attempt 16-FEB
18:08:51
Last start done 16-FEB 18:08:51 Last start failed
None
-- EXA Error Information 16-FEB-1993 18:10:26 --
Receive failures 0 Send failures
0
Unrec frame dest 0 Xmt coll chk failure
0
Data overrun 0 Transmit timeouts
0
System buff unavail 0 Excessive collisions
0
User buff unavail 0 Last exc collision
0
Frames lost, hw buff 0 No work transmits
311708
Invalid length 0 Bad PTE transmits
0
Invalid length (2 sh) 0
Fatal error count 0 RDL errors
0
Transmit timeouts 0 Last fatal error
None
Restart failures 0 Prev fatal error
None
Power failures 0 Last error CSR
00000000
Hardware errors 0 Fatal error code
None
Control timeouts 0 Prev fatal error
None
-- EXA1 60-07 (SCA) Counters Information 16-FEB-1993 18:10:27 --
Last receive 16-FEB 18:10:27 Last transmit 16-FEB
18:10:27
Octets received 67737813 Octets sent
95720809
PDUs
-- EXA1 60-07 (SCA) Counters Information 16-FEB-1993 18:10:27 --
Last receive 16-FEB 18:10:27 Last transmit 16-FEB
18:10:27
Octets received 67737813 Octets sent
95720809
PDUs received 338818 PDUs sent
482387
Mcast octets received 0 Mcast octets sent
0
Mcast PDUs received 0 Mcast PDUs sent
0
Unavail user buffer 0 Last start attempt
None
Last start done 16-FEB 15:53:01 Last start failed
None
-- EXA3 60-03 (DECNET) Counters Information 16-FEB-1993 18:10:27
--
Last receive None Last transmit 16-FEB
18:10:12
Octets received 54103 Octets sent
18627
PDUs received 1029 PDUs sent
357
Mcast octets received 0 Mcast octets sent
0
Mcast PDUs received 0 Mcast PDUs sent
0
Unavail user buffer 0 Last start attempt
None
Last start done 16-FEB 16:46:06 Last start failed
None
$ dir ssddhv4*
%DIRECT-W-NOFILES, no files found
$
---------------------------------------------------
VAX/VMS System analyzer
-- LAN Device Summary 16-FEB-1993 18:22:18 --
LAN block address = 80FF3BD0 (2 stations)
LAN flags: 0002 LAN_init
LSB address = 80FFDFD0
Device state = 0013 Inited,Run,Timer
-- FXA Unit Summary 16-FEB-1993 18:22:18 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
FXA0 80FF3910
FXA1 810193D0 Eth 60-07 SCA 0017
Strtn,Len,Uniq,Strtd
FXA2 8118B180 Eth 60-03 DECNET 0007 Strtn,Len,Uniq
FXA3 8119DFC0 Eth 60-04 LAT 0015 Strtn,Uniq,Strtd
LSB address = 810083E0
Device state = 001B Inited,Run,Ctl_Rdy,Timer
-- EXA Unit Summary 16-FEB-1993 18:22:18 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EXA0 81007DC0
EXA1 8103FA90 Eth 60-07 SCA 0017
Strtn,Len,Uniq,Strtd
EXA3 8118AE70 Eth 60-03 DECNET 0017
Strtn,Len,Uniq,Strtd
$
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 864.1 | Is AUTOGEN happy? | CERN::JRS | John SHADE - 'Attila the Nun' | Wed Feb 17 1993 04:15 | 17 |
| I'll let someone else comment on the FX error count (other than to say that a
non-zero fatal error count is never normal ;-)). However, this may not be the
cause of your performance problems. RWSCS is usually indicative of a lot of
remote locking acitivity or a shortage of some SCS resource on a remote node.
It is a strange condition in that it is quite frequent, but the occurences
should be of such short duration as to be rarely noticeable.
Does the customer run AUTOGEN on all the nodes in the cluster every now and
again? Some possibilities that spring to mind are a shortage of MSCP buffers on
the remote node, some SCS-related parameters being too low (e.g. SCSCONNCNT,
SCSRESPCNT, and SCSBUFFCNT) or process quotas for the backup process that are
too generous.
Is RWSCS the only thing that's being complained about, or is backup performance
the real issue?
-John
|
| 864.2 | It's not connected. | USHS01::LIN | Terry Lin | Wed Feb 17 1993 16:02 | 6 |
| Thans for the reply John. I just found out that the customer didn't
have FDDI controller connected to FDDI ring. The error count
disappeared this morning when they connect the controller to the FDDI.
They have some other problem before they can test if the performance
improves or not.
|