Conference csc32::consolemanager

68.0. "%VCS-I-CDISABLE, System xxxxxx has been disabled" by KETJE::STEUKERS () Fri Apr 09 1993 12:24

Hi,




In attachment follows an extract from a note out of the VCS conference.
The problem is that the Ultrix console lines get diabled at random and a
VCS reconfigure does not cure the problem. I think the problem bopils down
to the I/O buffering of the console line on the Ultrix machine.

Can some U*ix expert explain what is possible on the level of console line
setting on Ultrix? 

Thanks on forehand,
Erik.


================================================================================
Note 1195.4     %VCS-I-CDISABLE, System xxxxxx has been disabled          4 of 8
KETJE::STEUKERS                                      20 lines  26-MAR-1993 12:26
                         -< VCS-I-CDISABLE at random >-
--------------------------------------------------------------------------------
Hi,




I have a customer who uses VCS with 8 systems hooked up to a DS300 and fed into
a VS3100-M38.

Five of these systems are VAXes (4000 and 6000 systems), the three others are
RISC machine type DS5000/240. At regular times(the environment is running for
about 6 months now) one or more lines (randomly) loose connection to the RISC
systems get DIASABLED. Sometimes some lines are already disabled at reboot time.
A VCS reconfigure does not cure the problem. Its is allways the RISC systems wich
lose connection.


They run VMS5.5-2 and VCS1.4 (not the latest patch kit applied).

Any hints?
Erik.  
================================================================================
Note 1195.5     %VCS-I-CDISABLE, System xxxxxx has been disabled          5 of 8
CSC32::BUTTERWORTH                                    3 lines  26-MAR-1993 13:50
--------------------------------------------------------------------------------
    Check for differences inthe config of the two failing ports. VCS
    doesn't really care whats it's "talking" too. This should be troubled
    shooted as a server problem.
================================================================================
Note 1195.6     %VCS-I-CDISABLE, System xxxxxx has been disabled          6 of 8
KETJE::STEUKERS                                      14 lines  30-MAR-1993 05:20
                    -< Terminal server port setup is equal >-
--------------------------------------------------------------------------------
	Dan,



	The terminal server port setup is equal for both type of machines.
	Both terminal lines on the host platforms are 8BITs NOPARITY.

	As I said the failing ports fail dynamically, I mean one time it is
	port 3 and 5, the other time it is 3 and 4, another time it is port 5
	(its allways an Ultrix port that fails).
	But most of the time it works, wich is peculiar. Could the NOPARITY
	definition have to do with is?
	
	Erik.
================================================================================
Note 1195.7     %VCS-I-CDISABLE, System xxxxxx has been disabled          7 of 8
CSC32::BUTTERWORTH                                   19 lines  30-MAR-1993 16:40
--------------------------------------------------------------------------------
    Erik,  
       Typically 8 bits, noparity is what is used. However, I remember
    a peculiarity of U*x systems such that parity may change during
    bootstrap. I remember a system running 4.2 BSD Unix that was 8
    bits, no parity when in console mode. Booting the OS changed the config
    to 7 bits, even parity or some such. I remeber that we had to edit the
    ttytab file or somehting like that so that the OS didn't change the
    setting. Bottom line is this could effect flow-control detection if the
    term port is expecting one parity and the service node isn't speaking
    the same parity. Attach to the terminal server and do
    
    Local>SHO PORT x COUNTER
    
    Look for framing errors and data overruns and such. See an Unix
    hack for info on the ttytab file mentioned above.
    
    Regs,
      Dan
    
================================================================================
Note 1195.8     %VCS-I-CDISABLE, System xxxxxx has been disabled          8 of 8
KETJE::STEUKERS                                      15 lines   9-APR-1993 06:08
                          -< Errors on Tserver ports >-
--------------------------------------------------------------------------------
	Hi,


	The customer indeed has errors on port level for the Ultrix systems.

	The terminal server has an uptime of 161 days, one port indicates
	22587 Overrun errors (no other errors), another one had 73 overrun errors
	(no other errors) and the third one had 500 framing errors. The ports
	used for VMS systems had no errors at all.

	I will crosspost the note in the console-manager notes file to see
	if something of our U*ix community can give some advise on the ttytab
	file.

	Erik.

    
    
    Nobody with the same problem or can help us ?
    
    Thanks in advance,
    
    Geert

Hi,
   we have run several ULTRIX systems with console
manager using the hardwired line, LAT and TELNET
connect functions and have not seen your problem.

For information how often do you see the problem
with the disconnects?

Below is the charecteristics of our console devices:

# stty everything > /dev/console
old tty, speed 9600 baud , 0 rows, 0 columns
-parity raw -nl -echo -lcase -tandem tabs -cbreak ff1
erase  kill   intr   quit   stop   eof
^?     ^U     ^C     ^\     ^S/^Q  ^D
#

This is what is set by default when the system boots.
We have not changed that at all.


Cheers Simon....