|
|
1.1 root 1: \" @(#)hyroute.8 2.1 Hyperchannel Routing Daemon 11/29/82
2: .TH HYROUTE 8
3: .UC 4
4: .SH NAME
5: hyroute \- set the hyperchannel routine tables
6: .SH SYNOPSIS
7: .B hyroute
8: [
9: .B \-s
10: ] [
11: .B \-p
12: ] [
13: .B \-c
14: ] [
15: .B \-l
16: ] [
17: .B \-d
18: ] [
19: .I file
20: ]
21: .br
22: .SH DESCRIPTION
23: .I Hyroute
24: manipulates the Hyperchannel routing information.
25: .PP
26: With the
27: .B \-s
28: option, it reads
29: .I file
30: and sets the system's database according to the information in the file (see below).
31: If no input file is given, or if the argument `\-' is encountered,
32: .I hyroute
33: reads from standard input.
34: .PP
35: The
36: .B \-c
37: option causes hyroute to compare the system's current information to
38: that contained in
39: .IR file .
40: .PP
41: The
42: .B \-p
43: option causes a digested version of
44: .I file
45: to be printed.
46: .PP
47: The \-d
48: option causes a "dump" of the system's table (used for debugging routing code).
49: .SH "FILE FORMAT"
50: The input file is free format.
51: Comment lines start with a '*' in column one.
52: Statements end with a semicolon.
53: .PP
54: .ti +1i
55: .B direct
56: .I host dest control access ;
57: .PP
58: Describes a host that can be directly reached from this adapter.
59: .I Host
60: is a host name as listed /usr/lib/hosts,
61: .IR dest ,
62: .IR control ,
63: and
64: .I access
65: are hexadecimal numbers.
66: The data will be send to hyperchannel address
67: .I dest
68: using a control
69: value of
70: .I control
71: and an access code of
72: .I access
73: (see adapter manuals for details).
74: .PP
75: The specified remote adapter and the local adapter must both be connected to
76: one or more common trunks
77: or connected to trunks that are connected with with link adapters.
78: .PP
79: .ti +1i
80: .B gateway
81: .I host gate1 gate2 gate3 ... ;
82: .PP
83: Describes a host that must be reached indirectly through any one of the hosts indicated by
84: .IR gate n.
85: The hosts listed are not gateways in the formal sense
86: (they don't run the internet gateway protocols),
87: but are hosts on the hyperchannel can "bridge" between subsections of the hyperchannel network.
88: .PP
89: A sample file follows:
90: .PP
91: .in +1i
92: .nf
93: * comment
94: direct azure 6100 0 0;
95: direct bronze 6101 0 0;
96: direct cyber 2100 1100 0;
97: direct dadcad 6102 0 0;
98: direct tekcad 2400 1100 0;
99: direct tekcrd 2201 1100 0;
100: direct tekid 2500 1100 0;
101: direct teklabs 2200 1100 0;
102: gateway iddic tekcrd teklabs cyber tekcad tekid;
103: gateway iddme tekcrd teklabs cyber tekcad tekid;
104: gateway metals tekcrd teklabs cyber;
105: .in -1i
106: .fi
107: .PP
108: .SH "SEE ALSO"
109: hy(4)
110: .SH FILES
111: .ta +1i
112: /dev/hy character special file to get to the interface
113: (only has an ioctl entry)
114: .SH BUGS
115: Probably.
116: .SH AUTHOR
117: Steve Glaser, Tektronix Inc.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.