![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to mpcctab.4 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / usr.sbin / dlmpcc|
Return to mpcctab.4 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / usr.sbin / dlmpcc |
1.1 root 1: .\" Copyright (c) 1987 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" This code is derived from software contributed to Berkeley by
5: .\" Computer Consoles Inc.
6: .\"
7: .\" Redistribution and use in source and binary forms are permitted provided
8: .\" that: (1) source distributions retain this entire copyright notice and
9: .\" comment, and (2) distributions including binaries display the following
10: .\" acknowledgement: ``This product includes software developed by the
11: .\" University of California, Berkeley and its contributors'' in the
12: .\" documentation or other materials provided with the distribution and in
13: .\" all advertising materials mentioning features or use of this software.
14: .\" Neither the name of the University nor the names of its contributors may
15: .\" be used to endorse or promote products derived from this software without
16: .\" specific prior written permission.
17: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
18: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
19: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
20: .\"
21: .\" @(#)mpcctab.4 6.4 (Berkeley) 6/23/90
22: .\"
23: .TH MPCCTAB 4 "June 23, 1990"
24: .UC 7
25: .SH NAME
26: mpcctab \- MPCC configuration file
27: .SH DESCRIPTION
28: The file \fBmpcctab\fR is used to configure CCI's Multi-Protocol
29: Communication Controller (MPCC).
30: The controller provides high-speed
31: synchronous communications for the \s-1POWER 6\s+1 family
32: of computers.
33: This file determines the MPCC board
34: configurations. You can download either a synchronous , bisync or
35: an asynchronous protocol to an MPCC board.
36: See \fIdlmpcc\fR(8)
37: for details.
38: .LP
39: A \fBmpcctab\fR file is supplied
40: with each MPCC release; however,
41: you can modify this file or create your own file
42: by using one of the \s-1UNIX\s+1 text editors.
43: .LP
44: The contents of the file
45: consists of entries that describe supported communication
46: protocols and their unique attributes. The protocols supported are
47: X.25, SNA, ASYNC, and BISYNC.
48: For ASYNC two different entries are possible in the
49: \fIprocol\fR field - if 16 port MPCC async is configured, then ASYNC is
50: entered; 32 port MPCC async is specified by entering 32PORT.
51: This file must reside in the directory
52: \fB/etc/mpcc\fR.
53: .SH Entry Line Format
54: An entry line consists of an \fIitem identifier\fR followed by
55: variable width arguments separated by colons. There are three
56: item identifiers: MPCC, PROTOCOL, PORT. The MPCC line in this file
57: identifies the board number. The PROTOCOL line identifies
58: the specific communication protocol.
59: The PORT line describes
60: the port for the immediately preceding protocol. The number
61: of arguments for the PROTOCOL and PORT lines,
62: and the arguments themselves,
63: are protocol dependent. See the individual
64: argument descriptions for details.
65: .LP
66: Notes: Use upper case letters for clarity when specifying the item
67: identifier and the protocol name. Make sure that you enter
68: the argument values in the order specified below. Also, use comments
69: liberally, and indicate comment lines by placing a
70: pound sign (\fB#\fR) in column one.
71: .LP
72: The item identifiers and their corresponding line
73: formats, with valid argument values, follow:
74: .LP
75: \fBMPCC Line\fR
76: .LP
77: Format:
78: .RS
79: .LP
80: \fBMPCC:\fIbdno\fB:\fR[\fBFCCS,\fIportno\fR\fB,\fItimer\fR]\fB:\fR[\fBSOC,\fIportno\fR]
81: .RE
82: .LP
83: Argument Explanations:
84: .RS
85: .IP \fIbdno\fR 8
86: Specifies the board number.
87: .IP \fBFCCS\fR 8
88: FCCS is a fault-tolerant support system that allows backup ports
89: to assume the functions of failed ports.
90: For example,
91: if port 0 fails for any reason,
92: another port may be configured to assume the duties of the failed port.
93: The keyword \fBFCCS\fR identifies this feature and must be
94: followed by the list of fail-safe port numbers and a time increment,
95: described below.
96: This feature is optional.
97: .IP \fBSOC\fR 8
98: An FCCS port can also be an SOC (Switch On Close) port,
99: meaning that the port will switch when it is closed.
100: And as with FCCS, the port will switch if it fails.
101: This feature is optional.
102: .IP \fIportno\fR 8
103: Portno is a list of port numbers,
104: separated by commas,
105: specifying the primary ports you want protected by backup ports.
106: FCCS boards have either 4 primary and 4 backup ports,
107: or 8 primary and 8 backup ports.
108: The valid port numbers are
109: .B 0
110: through
111: .B 3
112: for the 4-port version,
113: and
114: .B 0
115: through
116: .B 7
117: for the 8-port version.
118: .IP
119: Each of the ports has a switched connector.
120: If the board fails for any reason,
121: the traffic on these ports is automatically routed
122: through the switched connector.
123: These connectors must be cabled to secondary ports on the other FCCS
124: connector panels.
125: The secondary ports are numbered 8 through 11 on the 4-port version and
126: 8 through 15 on the 8-port version.
127: Only the primary ports need be designated in the FCCS configuration line,
128: however all ports must be identified as described in the PORT Line section
129: below.
130: .if n .bp
131: .IP \fItime\fR 8
132: Specifies the time period for the sentinel relay timer.
133: Each board resets its sentinel timer after the specified
134: time period. If the
135: board fails, and therefore can't set the timer, then control
136: is passed automatically to another board, which continues
137: the current processing. This feature ensures PerpetualProcessing
138: and is transparent to the user. The valid range of values
139: in milliseconds is from \fB50\fR to \fB5950\fR in
140: 50 millisecond increments.
141: .LP
142: .RE
143: \fBPROTOCOL Line\fR
144: .LP
145: Format:
146: .LP
147: .RS
148: \fBPROTOCOL:\fIprocol\fB:\fIdepargs\fR
149: .LP
150: .RE
151: Argument Explanations:
152: .RS
153: .IP \fIprocol\fR 10
154: Specifies the protocol you want associated with the
155: board specified in the previous \fBMPCC\fR line.
156: .IP \fIdepargs\fR 10
157: Specifies the protocol-dependent protocol attributes. X.25 and SNA have ten (10)
158: arguments,
159: ASYNC has just one (1) argument, and BISYNC has no arguments.
160: .LP
161: .cu
162: X.25 Dependent Attributes
163: .LP
164: Note: You must be familiar with the
165: X.25 CCITT Yellow Book (1980)
166: in order to understand the following values.
167: .IP \fIN1\fR 8
168: Specifies the maximum frame size in bytes.
169: .IP \fIN2\fR 8
170: Specifies the retry count.
171: .IP \fIT1\fR 8
172: Specifies the retry timer in milliseconds.
173: .IP \fIT2\fR 8
174: Specifies the response delay timer in milliseconds.
175: .IP \fIT3\fR 8
176: Specifies the inactive link timer in milliseconds.
177: .IP \fIT4\fR 8
178: Specifies the idle channel timer in milliseconds.
179: .IP \fIK\fR 8
180: Specifies the Level 2 window size.
181: .if n .bp
182: .IP \fIxid1\fR 8
183: Specifies the destination type in the XID command. It must be a number
184: from 1-5:
185: .nf
186:
187: 1 = AXE
188: 2 = CTSS
189: 3 = DEX
190: 4 = DMS
191: 5 = WESCOM
192: .fi
193: .IP \fIxid2\fR 8
194: Specifies the destination identity in the XID command. It can be three to
195: nine ASCII characters.
196: .IP \fIxid3\fR 8
197: Specifies the additional information in the XID command. It can be any
198: ASCII string up to 20 characters long.
199: .LP
200: .cu
201: ASYNC and 32PORT Dependent Attribute
202: .IP \fIbufsize\fR 10
203: Specifies the size of the transmit/receive buffers in bytes.
204: .RE
205: .LP
206: \fBPORT Line\fR
207: .LP
208: Format:
209: .LP
210: .RS
211: \fBPORT:\fIportno\fB:\fIprocol\fB:\fIdepargs\fR
212: .RE
213: .LP
214: Argument Explanations:
215: .RS
216: .IP \fIportno\fR 10
217: Specifies the port number of the previously specified board.
218: .IP \fIprocol\fR 10
219: Specifies the protocol. You must state the same protocol
220: as you stated in the preceding PROTOCOL line.
221: .IP \fIdepargs\fR 10
222: Specifies the protocol-dependent port attributes. X.25 has
223: fourteen (14) arguments. ASYNC, 32PORT and BISYNC have none. SNA has 14
224: fixed arguments.
225: .LP
226: .cu
227: X.25 Dependent Arguments
228: .LP
229: Note: You must be familiar with the X.25 CCITT Yellow
230: Book (1980) in order to understand the following values.
231: .IP \fIixmitbuf\fR 12
232: Specifies the number of transmit buffers allocated
233: for I frames.
234: .IP \fIsuxmitbuf\fR 12
235: Specifies the number of transmit buffers allocated for
236: S/U frames.
237: .IP \fIirecvbuf\fR 12
238: Specifies the number of receive buffers allocated for
239: I frames.
240: .IP \fIsurecvbuf\fR 12
241: Specifies the number of receive buffers allocated for
242: S/U frames.
243: .IP \fIxmito\fR 12
244: Specifies the Level 1 transmit timeout.
245: This argument should be \fB0\fR so that Level 1 calculates timeout from
246: the baud rate.
247: .IP \fIrts\fR 12
248: Specifies the modem control value
249: for rts. Valid values are \fB1\fR which equals
250: \fBassert\fR, \fB2\fR which equals \fBdrop\fR, and \fB3\fR
251: which equals \fBauto\fR.
252: .IP \fIdtr\fR 12
253: Specifies the modem control value for dtr.
254: Valid values are \fB1\fR which equals
255: \fBassert\fR, and \fB2\fR which equals \fBdrop\fR.
256: .IP \fIlineidle\fR 12
257: Specifies the line state between transmissions.
258: Valid values are \fB0\fR which specifies a flag
259: fill, and \fB1\fR which specifies a mark fill.
260: .IP \fIrcvadr\fR 12
261: Specifies the port configuration. A \fB1\fR makes the port
262: a DCE, while a \fB3\fR makes the port a DTE.
263: .IP \fImask\fR 12
264: Specifies the data link receive mask. This argument must be
265: \fB3\fR.
266: .IP \fIxmtrty\fR 12
267: Specifies the number of data link retries after a transmit
268: timeout. This argument should be zero since upper levels of X25 do retries.
269: .IP \fIbaud\fR 12
270: Specifies the baud rate of a transmission. All standard rates
271: are supported. Some common rate values are \fB0\fR equals a modem,
272: \fB13\fR equals 9600, and \fB26\fR equals 56KB. See the header file
273: \fBmp_port.h\fR for other values.
274: .IP \fIencode\fR 12
275: Specifies the physical data encoding. A \fB0\fR indicates NRZ, and a \fB1\fR
276: indicates NRZI.
277: .IP \fItrace\fR 12
278: Specifies the data link receive trace mode. This argument must be \fB0\fR.
279: .RE
280: .if n .bp
281: .SH EXAMPLE
282: The following entry configures five MPCC boards: one for X.25,
283: ASYNC, 32PORT, BISYNC and SNA. Each has two ports.
284: .nf
285:
286: MPCC:0
287: PROTOCOL:X25:272:2:6000:1000:30000:20000:8:2:ccice1:remote
288: PORT:0:X25:8:16:8:16:0:1:1:0:1:3:0:0:0:0
289: PORT:1:X25:8:16:8:16:0:1:1:0:3:3:0:0:0:0
290:
291: MPCC:1
292: PROTOCOL:ASYNC:128
293: PORT:0:ASYNC
294: PORT:1:ASYNC
295:
296: MPCC:2
297: PROTOCOL:32PORT:128
298: PORT:0:32PORT
299: PORT:1:32PORT
300:
301: MPCC:3
302: PROTOCOL:BISYNC
303: PORT:0:BISYNC
304: PORT:1:BISYNC
305:
306: MPCC:4
307: PROTOCOL:SNA:272:4:800:200:20000:20000:8:2:acey:deucy
308: PORT:0:SNA:8:10:10:24:5:3:1:0:193:193:1:0:0:0
309: PORT:1:SNA:8:10:10:24:5:3:1:0:193:193:1:0:0:0
310: .fi
311: .SH FILES
312: /etc/mpcctab
313: /etc/mpcca
314: /etc/mpccb
315: /etc/mpcc32
316: /etc/mpccx
317: .SH SEE ALSO
318: dlmpcc(8)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.