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