mpcctab man page on 4.4BSD

Man page or keyword search:  
man Server   1065 pages
apropos Keyword Search (all sections)
Output format
4.4BSD logo
[printable version]

MPCCTAB(4)		 BSD Kernel Interfaces Manual		    MPCCTAB(4)

     mpcctab — MPCC configuration file

     The ASCII file mpcctab is used to configure CCI's Multi-Protocol Communi‐
     cation Controller (MPCC).	The controller provides high-speed synchronous
     communications for the POWER family of computers.	This file determines
     the MPCC board configurations. You can download either a synchronous ,
     bisync or an asynchronous protocol to an MPCC board.  (See dlmpcc(8) for

     A mpcctab file is supplied with each MPCC release; however, you can mod‐
     ify this file or create your own file.

     The contents of the file consists of entries that describe supported com‐
     munication protocols and their unique attributes. The protocols supported
     are X.25, SNA, ASYNC, and BISYNC.	For ASYNC two different entries are
     possible in the procol field - if 16 port MPCC async is configured, then
     ASYNC is entered; 32 port MPCC async is specified by entering 32PORT.
     This file must reside in the directory /usr/libdata.

Entry Line Format
     An entry line consists of an item identifier followed by variable width
     arguments separated by colons. There are three item identifiers: MPCC,
     PROTOCOL, PORT.  The MPCC line in this file identifies the board number.
     The PROTOCOL line identifies the specific communication protocol.	The
     PORT line describes the port for the immediately preceding protocol. The
     number of arguments for the PROTOCOL and PORT lines, and the arguments
     themselves, are protocol dependent. See the individual argument descrip‐
     tions for details.

     Notes: Use upper case letters for clarity when specifying the item iden‐
     tifier and the protocol name. Make sure that you enter the argument val‐
     ues in the order specified below. Also, use comments liberally, and indi‐
     cate comment lines by placing a pound sign (#) in column one.

     The item identifiers and their corresponding line formats, with valid
     argument values, follow:

     MPCC Line



     Argument Explanations:

	   bdno	   Specifies the board number.

	   FCCS	   FCCS is a fault-tolerant support system that allows backup
		   ports to assume the functions of failed ports.  For exam‐
		   ple, if port 0 fails for any reason, another port may be
		   configured to assume the duties of the failed port.	The
		   keyword FCCS identifies this feature and must be followed
		   by the list of fail-safe port numbers and a time increment,
		   described below.  This feature is optional.

	   SOC	   An FCCS port can also be an SOC (Switch On Close) port,
		   meaning that the port will switch when it is closed.	 And
		   as with FCCS, the port will switch if it fails.  This fea‐
		   ture is optional.

	   portno  Portno is a list of port numbers, separated by commas,
		   specifying the primary ports you want protected by backup
		   ports.  FCCS boards have either 4 primary and 4 backup
		   ports, or 8 primary and 8 backup ports.  The valid port
		   numbers are 0 through 3 for the 4-port version, and 0
		   through 7 for the 8-port version.

		   Each of the ports has a switched connector.	If the board
		   fails for any reason, the traffic on these ports is auto‐
		   matically routed through the switched connector.  These
		   connectors must be cabled to secondary ports on the other
		   FCCS connector panels.  The secondary ports are numbered 8
		   through 11 on the 4-port version and 8 through 15 on the
		   8-port version.  Only the primary ports need be designated
		   in the FCCS configuration line, however all ports must be
		   identified as described in the PORT Line section below.

	   time	   Specifies the time period for the sentinel relay timer.
		   Each board resets its sentinel timer after the specified
		   time period. If the board fails, and therefore can't set
		   the timer, then control is passed automatically to another
		   board, which continues the current processing. This feature
		   ensures “PerpetualProcessing” and is transparent to the
		   user. The valid range of values in milliseconds is from 50
		   to 5950 in 50 millisecond increments.

     PROTOCOL Line



     Argument Explanations:

	   procol  Specifies the protocol you want associated with  the	 board
		   specified in the previous MPCC line.

		   Specifies the protocol-dependent protocol attributes.  X.25
		   and SNA have ten (10) arguments, ASYNC has just one 1 argu‐
		   ment, and BISYNC has no arguments.

	   X.25 Dependent Attributes

	   Note:  You  must be familiar with the X.25 CCITT Yellow Book (1980)
	   in order to understand the following values.

	   N1	   Specifies the maximum frame size in bytes.

	   N2	   Specifies the retry count.

	   T1	   Specifies the retry timer in milliseconds.

	   T2	   Specifies the response delay timer in milliseconds.

	   T3	   Specifies the inactive link timer in milliseconds.

	   T4	   Specifies the idle channel timer in milliseconds.

	   K	   Specifies the Level 2 window size.

	   xid1	   Specifies the destination type in the XID command. It  must
		   be a number from 1-5:

			 1 = AXE
			 2 = CTSS
			 3 = DEX
			 4 = DMS
			 5 = WESCOM

	   xid2	   Specifies  the  destination identity in the XID command. It
		   can be three to nine ASCII characters.

	   xid3	   Specifies the additional information in the XID command. It
		   can be any ASCII string up to 20 characters long.

	   ASYNC and 32PORT Dependent Attribute

		   Specifies  the  size	 of  the  transmit/receive  buffers in

     PORT Line



     Argument Explanations:

	   portno  Specifies the  port	number	of  the	 previously  specified

	   procol  Specifies the protocol. You must state the same protocol as
		   you stated in the preceding PROTOCOL line.

		   Specifies the protocol-dependent port attributes. X.25  has
		   fourteen  (14)  arguments.	ASYNC,	32PORT and BISYNC have
		   none.  SNA has 14 fixed arguments.

	   X.25 Dependent Arguments

	   Note: You must be familiar with the X.25 CCITT Yellow  Book	(1980)
	   in order to understand the following values.

	   ixmitbuf   Specifies the number of transmit buffers allocated for I

	   suxmitbuf  Specifies the number of transmit buffers	allocated  for
		      S/U frames.

	   irecvbuf   Specifies	 the number of receive buffers allocated for I

	   surecvbuf  Specifies the number of receive  buffers	allocated  for
		      S/U frames.

	   xmito      Specifies	 the  Level 1 transmit timeout.	 This argument
		      should be 0 so that Level 1 calculates timeout from  the
		      baud rate.

	   rts	      Specifies	 the modem control value for rts. Valid values
		      are 1 which equals assert, 2 which equals	 drop,	and  3
		      which equals auto.

	   dtr	      Specifies the modem control value for dtr.  Valid values
		      are 1 which equals assert, and 2 which equals drop.

	   lineidle   Specifies the line state between	transmissions.	 Valid
		      values  are  0  which specifies a flag fill, and 1 which
		      specifies a mark fill.

	   rcvadr     Specifies the port configuration. A 1 makes the  port  a
		      DCE, while a 3 makes the port a DTE.

	   mask	      Specifies the data link receive mask. This argument must
		      be 3.

	   xmtrty     Specifies the number of data link retries after a trans‐
		      mit  timeout.  This  argument should be zero since upper
		      levels of X25 do retries.

	   baud	      Specifies the baud rate of a transmission. All  standard
		      rates  are  supported.  Some  common  rate  values are 0
		      equals a modem, 13 equals 9600, and 26 equals 56KB.  See
		      the header file mp_port.h for other values.

	   encode     Specifies the physical data encoding. A 0 indicates NRZ,
		      and a 1 indicates NRZI.

	   trace      Specifies the data link receive trace mode.  This	 argu‐
		      ment must be 0.

     The following entry configures five MPCC boards: one for X.25, ASYNC,
     32PORT, BISYNC and SNA.  Each has two ports.








     The mpcc configuration file appeared in 4.3BSD-Tahoe.

BSD				 May 10, 1991				   BSD

List of man pages available for 4.4BSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net