2 .\" ===================================
3 .\" HARP | Host ATM Research Platform
4 .\" ===================================
7 .\" This Host ATM Research Platform ("HARP") file (the "Software") is
8 .\" made available by Network Computing Services, Inc. ("NetworkCS")
9 .\" "AS IS". NetworkCS does not provide maintenance, improvements or
10 .\" support of any kind.
12 .\" NETWORKCS MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED,
13 .\" INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY
14 .\" AND FITNESS FOR A PARTICULAR PURPOSE, AS TO ANY ELEMENT OF THE
15 .\" SOFTWARE OR ANY SUPPORT PROVIDED IN CONNECTION WITH THIS SOFTWARE.
16 .\" In no event shall NetworkCS be responsible for any damages, including
17 .\" but not limited to consequential damages, arising from or relating to
18 .\" any use of the Software or related support.
20 .\" Copyright 1994-1998 Network Computing Services, Inc.
22 .\" Copies of this Software may be made, however, the above copyright
23 .\" notice must be reproduced on all copies.
25 .\" @(#) $FreeBSD: src/sbin/atm/atm/atm.8,v 1.3.2.2 2002/12/29 16:35:37 schweikh Exp $
26 .\" @(#) $DragonFly: src/sbin/atm/atm/atm.8,v 1.2 2003/06/17 04:27:32 dillon Exp $
29 .de EX \"Begin example
42 .TH ATM 8 "1998-08-20" "HARP"
44 atm \- user configuration and display command for HARP ATM interface
46 Interface management subcommands:
56 <interface> <MAC/ESI address>
59 <interface> <prefix> <count>
62 <interface> <NSAP prefix>
73 .B atm show stats interface
74 [<interface> [phy | dev | atm | aal0 | aal4 | aal5 | driver]]
77 VCC management subcommands:
80 <interface> <vpi> <vci> <aal> <encaps> <owner> ...
83 <interface> <vpi> <vci>
86 <interface> <vpi> <vci>
89 [<interface> [<vpi> [<vci>]]]
92 [<interface> [<vpi> [<vci>] | SVC | PVC]]
95 IP management subcommands:
98 [<netif>] <host> <ATM address>
101 <interface> <vpi> <vci> <aal> <encaps> IP <netif> <host> | dynamic
107 <netif> <ATM address> | local [<IP prefix> ...]
112 .B atm show arpserver
120 Miscellaneous subcommands:
129 configures and displays the status of the Host ATM Research Platform
130 (HARP) networking software.
131 The subcommands fall into several categories:
133 \fIInterface management\fP subcommands allow manipulation of the
135 Functions include assigning a signalling manager to an interface,
136 setting the ATM address, associating network interfaces with
137 an interface, and displaying information about interfaces.
139 \fIVCC management\fP subcommands allow for managing ATM virtual
140 channel connections (VCCs).
141 Functions include opening and closing VCCs and displaying information
144 \fIIP management\fP subcommands allow for managing the interface
145 between IP and the ATM software.
146 Functions include displaying and manipulating the ATMARP cache,
147 opening a PVC connected to IP,
148 assigning an ATMARP server to a network interface,
149 and displaying information about IP VCCs.
151 \fIMiscellaneous\fP subcommands allow for displaying the version
152 of the ATM software and for getting help with the \fIatm\fP command.
153 .SS "Signalling Managers"
154 The signalling manager is responsible for the opening and closing of
156 Four signalling managers are supported:
162 SPANS - supports SPANS, FORE's proprietary signalling protocol,
164 UNI 3.0 - supports the signalling protocol from The ATM Forum's
165 \fIATM User-Network Interface Specification, Version 3.0\fP.
167 UNI 3.1 - supports the signalling protocol from The ATM Forum's
168 \fIATM User-Network Interface Specification, Version 3.1\fP.
171 All four signalling managers support the opening and closing of PVCs
172 (see the \fIadd\fP and \fIdelete\fP subcommands).
174 A signalling manager must be attached to a physical interface
175 (see the \fIattach\fP subcommand)
176 before any VCCs can be created on the interface.
177 .SS "Physical and Network Interfaces"
178 Two types of interfaces are supported:
179 physical interfaces and network interfaces.
180 A physical interface represents a physical point of attachment to an
182 A physical interface has an ATM address associated with it, except
183 when the PVC-only signalling manager is being used.
185 A network interface is a logical interface.
186 One or more network interfaces are associated with a physical
187 interface; each network interface has an IP address associated with it.
188 For UNI-controlled interfaces, there can be up to 256 network
189 interfaces associated with a physical interface.
190 In this case, the correspondence between the network interface and
191 the ATM address is determined by the selector field (the last
192 byte) of the physical interface's ATM address.
193 For PVC-only interfaces, there can be up to 256 logical interfaces
194 associated with each physical interface.
195 For interfaces controlled by the SPANS signalling manager,
196 there must be one and
197 only one network interface associated with each physical interface.
198 .SS "Keyword and Documentation Conventions"
199 Command and subcommand keywords can be abbreviated by simply giving
200 enough of the first part of the keyword to make it unique.
201 Thus, \fIatm sh v\fB gives the same result as \fIatm show vcc\fB.
203 All keywords are case-insensitive.
205 Where a host address needs to be given to the \fIatm\fP command,
206 either a DNS name or an IP address in dotted decimal format can
209 ATM addresses are specified as strings of hex digits, with an
210 optional leading "0x".
211 Fields within the address may be separated by periods, but periods
212 are for readability only and are ignored.
213 SPANS addresses are 8 bytes long, while NSAP-format addresses
215 The full address, including any leading zeroes, must be given.
218 0x47.0005.80.ffe100.0000.f21a.0170.0020481a0170.00 (NSAP format)
220 0x00000010.f2050aa9 (SPANS format)
224 .SS Interface Management Subcommands:
227 \fIatm add PVC <interface> <vpi> <vci> <aal> <encaps> <owner> ...\fP
230 the format of the \fIadd PVC\fP subcommand varies depending on the
232 See the description under "IP Management Subcommands."
234 \fIatm attach <interface> <sigmgr>\fP
239 \fI<interface>\fP specifies the physical interface to which the
240 signalling manager is to be attached,
242 \fI<sigmgr>\fP specifies which signalling manager is to be attached.
243 Valid choices are "SIGPVC", "SPANS", "UNI30", and "UNI31".
246 This command attaches a signalling manager to an interface.
247 Until this is done, VCCs cannot be opened or closed.
248 Only one signalling manager at a time can be attached to an interface.
250 \fIatm detach <interface>\fP
255 \fI<interface>\fP specifies the physical interface whose signalling
256 manager is to be detached.
259 This command detaches a signalling manager from an interface.
260 All VCCs that the signalling manager has created will be closed,
261 and no new VCCs can be created until a signalling manager (either
262 the same or a different one) is attached again.
264 \fIatm set MAC <interface> <MAC/ESI address>\fP
269 \fI<interface>\fP specifies the physical interface whose
270 MAC address is to be set,
272 \fI<MAC/ESI address>\fP specifies the 6-byte MAC part of the NSAP
273 address for the interface.
274 The MAC address is specified as a string of 12 hexadecimal
275 digits with an optional leading "0x".
276 Fields in the address may be separated by periods.
279 This command sets the MAC address for a UNI-controlled interface.
280 The first 13 bytes (the prefix) of the 20-byte NSAP-format address
281 are set by the \fIatm set prefix\fP command or the ILMI daemon
283 the next 6 bytes (the End System Identifier (ESI)) are set by
285 and the last byte (the selector) will be determined by which
286 network interface is to be associated with the address.
288 The \fIatm set MAC\fP command can be used to override the MAC
289 address in the interface hardware.
291 \fIatm set netif <interface> <prefix> <count>\fP
296 \fI<interface>\fP specifies the physical interface that the network
297 interface(s) are to be associated with,
299 \fI<prefix>\fP specifies the invariant part of the network
302 \fI<count>\fP specifies the number of network interface to be
306 This command creates one or more network interfaces and associates them
307 with the specified physical interface.
308 The network interface names are determined by the prefix and the count.
309 The names will be of the form <prefix><nn>, where <prefix> is the
310 prefix specified in the \fIset\fP subcommand and <nn> is a number
311 in the range 0 - <count>-1. For example, the command:
314 atm set netif hfa0 ni 2
316 would create two network interfaces, named ni0 and ni1, and associate
317 them with physical interface hfa0.
319 \fIatm set prefix <interface> <NSAP prefix>\fP
324 \fI<interface>\fP specifies the physical interface whose NSAP
327 \fI<NSAP prefix>\fP specifies the first 13 bytes of the NSAP address
329 The prefix is specified as a string of hexadecimal digits with an
330 optional leading "0x".
331 Fields in the prefix may be separated by periods.
334 This command sets the address for a UNI-controlled interface.
335 The first 13 bytes (the prefix) of the 20-byte NSAP-format address
336 are set by this command,
337 the next 6 bytes (the End System Identifier (ESI)) will be the
338 MAC address taken from the physical interface or set by the
339 \fIset MAC\fP subcommand,
340 and the last byte (the selector) will be determined by which
341 network interface is to be associated with the address.
343 The NSAP prefix must be set before a UNI-controlled
344 interface can become active.
345 This can be accomplished either by the ILMI daemon (\fIilmid\fP (8))
346 or the \fIset prefix\fP subcommand.
348 .I atm show config [<interface>]
350 displays the following information:
353 \- the name of the physical interface.
356 \- the name of the adapter vendor.
359 \- the model of the adapter.
362 \- the communications medium used by the adapter.
365 \- the type of bus the adapter is attached to.
368 \- the adapter's serial number.
371 \- the MAC address of the interface.
372 Note that this is the MAC address encoded in the hardware of
373 the adapter, even if the \fIatm set MAC\fP command has been used
374 to change the effective MAC address of the interface.
377 \- the hardware revision level reported by the interface.
380 \- the firmware revision level reported by the interface.
382 If no parameters are specified on the \fIshow config\fP subcommand,
383 the configurations of all physical interfaces will be displayed.
384 If an interface name is specified, only the configuration of the given
385 interface is displayed.
387 .I atm show interface [<interface>]
389 displays the following information:
392 \- the name of the physical interface.
395 \- the name of the signalling manager which has been attached to the
397 A dash (-) is shown if no signalling manager has been attached.
400 \- the state of the signalling manager for the interface.
401 Each signalling manager has its own set of states.
407 ACTIVE\ ---\ The signalling manager is active.
409 DETACH\ ---\ The signalling manager is being detached.
413 ACTIVE\ ---\ The signalling manager is active.
415 DETACH\ ---\ The signalling manager is being detached.
417 INIT\ -----\ The signalling manager's initial state.
419 PROBE\ ----\ The signalling manager is attempting to make
420 contact with the ATM switch.
424 NULL\ -----\ The signalling manager's initial state.
426 ADR_WAIT\ -\ The signalling manager is waiting for the NSAP
429 INIT\ -----\ The signalling manager is attempting to establish
430 contact with the switch.
432 ACTIVE\ ---\ The signalling manager is active.
434 DETACH\ ---\ The signalling manager is being detached.
438 \- the ATM address of the interface.
440 .B Network interfaces
441 \- the names of network interfaces, if any, associated with the
444 If no parameters are specified on the \fIshow interface\fP subcommand,
445 information about all physical interfaces will be displayed.
446 If an interface name is specified, only information about the given
447 interface is displayed.
449 .I atm show netif [<netif>]
451 displays the following information:
454 \- the name of the network interface.
457 \- the IP address of the network interface.
459 If no parameters are specified on the \fIshow netif\fP subcommand,
460 information about all network interfaces will be displayed.
461 If an interface name is specified, only information about the given
462 network interface is displayed.
464 \fIatm show stats interface [<interface> [phy | dev | atm | aal0 |
465 aal4 | aal5 | driver]]\fP
467 displays statistics associated with one or more interfaces.
468 Subject-area keywords
469 (\fIphy\fP, \fIdev\fP, \fIatm\fP, \fIaal0\fP,
470 \fIaal4\fP, \fIaal5\fP, or \fIdriver\fP)
471 can be specified to change the scope of the statistics displayed.
473 If no subject area keyword is specified, the following information is
477 \- the name of the physical ATM interface.
480 \- the number of Protocol Data Units (PDUs) which have been received
484 \- the number of bytes which have been received by the interface.
487 \- the number of input errors which the interface has experienced.
490 \- the number of Protocol Data Units (PDUs) which have been transmitted
494 \- the number of bytes which have been transmitted by the interface.
497 \- the number of output errors which the interface has experienced.
500 \- the number of command errors which the interface has experienced.
502 If a subject-area keyword is specified, then statistics for
503 that subject are displayed.
504 The statistics displayed depend on the adapter.
505 If requested statistics are not available for an adaptor,
506 an error will be noted.
508 If no parameters are specified on the \fIshow stats interface\fP
509 subcommand, statistics for all ATM interfaces are displayed.
510 If an interface name is specified, only statistics for the given
511 interface are displayed.
513 .SS VCC Management Subcommands:
515 \fIatm delete PVC <interface> <vpi> <vci>\fP
517 \fIatm delete SVC <interface> <vpi> <vci>\fP
522 \fIPVC\fP specifies that the VCC to be closed is a PVC,
524 \fISVC\fP specifies that the VCC to be closed is an SVC,
526 \fI<interface>\fP specifies the physical interface at which the
527 VCC to be closed terminates,
529 \fI<vpi>\fP specifies the Virtual Path Identifier (VPI) of the VCC,
531 \fI<vci>\fP specifies the Virtual Channel Identifier (VCI) of the VCC.
534 This command closes a VCC.
535 The two forms differ only in that the first specifies that the
536 VCC is a PVC (that was created by the \fIadd PVC\fP subcommand) and
537 the second specifies that the VCC is an SVC.
538 Reserved VCCs (with VCI values less than 32) cannot be closed
541 \fIatm show stats VCC [<interface> [<vpi> [<vci>]]]\fP
543 displays the following information:
546 \- the physical interface on which the VCC terminates.
549 \- the Virtual Path Identifier (VPI) for the VCC.
552 \- the Virtual Channel Identifier (VCI) for the VCC.
555 \- the number of Protocol Data Units (PDUs) which have been received
559 \- the number of bytes which have been received on the VCC.
562 \- the number of input errors which the VCC has experienced.
565 \- the number of Protocol Data Units (PDUs) which have been transmitted
569 \- the number of bytes which have been transmitted on the VCC.
572 \- the number of output errors which the VCC has experienced.
574 If no parameters are specified on the \fIshow VCC\fP subcommand, all
575 active VCCs are displayed.
576 If an interface name is specified, all active VCCs for the given
577 interface are displayed.
578 If an interface and VPI are specified, all active VCCs for the VPI
579 on the given interface are displayed.
580 If an interface, VPI, and VCI are specified, only the specified VCC on
581 the given interface is displayed (note that this could actually be
582 two VCCs, since SPANS considers SVCs to be unidirectional).
584 \fIatm show VCC [<interface> [<vpi> [<vci>] | SVC | PVC]]\fP
586 displays the following information:
589 \- the physical interface on which the VCC terminates.
592 \- the Virtual Path Identifier (VPI) for the VCC.
595 \- the Virtual Channel Identifier (VCI) for the VCC.
598 \- the ATM Adaptation Layer (AAL) in use on the VCC.
599 Possible values are null and AAL 1-5.
602 \- specifies whether the VCC is an SVC or a PVC.
605 \- the direction of information flow on the VCC.
606 VCCs can be inbound, outbound, or both.
609 \- the state of the VCC, as reported by the signalling manager.
610 Each signalling manager has its own set of states.
616 NULL\ -----\ No state.
618 ACTIVE\ ---\ The VCC is active.
620 FREE\ -----\ The VCC is closed and the signalling manager is waiting for
621 its resources to be freed.
625 NULL\ -----\ No state.
627 ACTIVE\ ---\ The VCC is a PVC and is active.
629 ACT_DOWN\ -\ The VCC is a PVC and the interface is down.
631 POPEN\ ----\ The VCC is being opened.
633 R_POPEN\ --\ The VCC is being opened by a remote host.
635 OPEN\ -----\ The VCC is active.
637 CLOSE\ ----\ The VCC is being closed.
639 ABORT\ ----\ The VCC is being aborted.
641 FREE\ -----\ The VCC is closed and the signalling manager is waiting for
642 its resources to be freed.
646 NULL\ -----\ No state.
648 C_INIT\ ---\ A VCC is being initiated.
650 C_OUT_PR\ -\ An outgoing VCC request is proceeding.
652 C_PRES\ ---\ A VCC is being initiated by the network.
654 CONN_REQ\ -\ A VCC request has been accepted by a HARP user.
656 C_IN_PR\ --\ An incoming VCC request is proceeding.
658 ACTIVE\ ---\ The VCC is active.
660 REL_REQ\ --\ The VCC is being closed.
662 REL_IND\ --\ The network is clearing a VCC.
664 SSCF_REC\ -\ The SSCF session on the signalling channel is in
665 recovery from an error.
667 FREE\ -----\ The VCC is closed and the signalling manager is waiting
668 for its resources to be freed.
670 ACT_DOWN\ -\ The VCC is a PVC and the interface is down.
674 \- the encapsulation in effect on the VCC.
675 Possible encapsulations are null and LLC/SNAP.
678 \- the owner or owners of the VCC.
679 Shows the name(s) of the function(s) using the VCC.
682 \- the ATM address of the host at the remote end of the VCC.
684 If no parameters are specified on the \fIshow VCC\fP subcommand, all
685 active VCCs are displayed.
686 If an interface name is specified, all active VCCs for the given
687 interface are displayed.
688 If an interface and VPI are specified, all active VCCs for the VPI
689 on the given interface are displayed.
690 If an interface, VPI, and VCI are specified, only the specified VCC on
691 the given interface is displayed (note that this could actually be
692 two VCCs, since SPANS considers SVCs to be unidirectional).
694 .SS IP Management Subcommands:
695 \fIatm add ARP [<netif>] <host> <ATM address>\fP
700 \fI<netif>\fP is the optional name of the network interface the
701 ATMARP entry is to be associated with.
702 If no name is specified, a network interface is chosen depending
703 on the IP address of the host being added.
705 \fI<host>\fP is the host name or IP address of the host to
706 be added to the ATMARP table,
708 \fI<ATM address>\fP is the ATM address of the host.
711 This command adds an entry to the ATMARP table for ATM.
712 The given host's IP address is associated with the given ATM address.
713 When IP needs to transmit data to the host, the specified ATM
714 address will be used to open an SVC.
716 The entry will be marked as permanent in the ATMARP table and will not
721 \fIatm add PVC <interface> <vpi> <vci> <aal> <encaps> IP <netif> <host> | dynamic\fP
727 \fI<interface>\fP specifies the physical interface where the PVC
730 \fI<vpi>\fP specifies the Virtual Path Identifier (VPI) of the PVC,
732 \fI<vci>\fP specifies the Virtual Channel Identifier (VCI) of the PVC,
734 \fI<aal>\fP specifies the ATM Adaptation Layer (AAL) for the PVC.
735 Valid choices are "null" or "AAL0" for the null AAL; "AAL1" for
736 AAL 1; "AAL2" for AAL 2; "AAL3", "AAL4", or "AAL3/4" for AAL 3/4;
737 and "AAL5" for AAL 5,
739 \fI<encaps>\fP specifies the encapsulation for the PVC.
740 Valid choices are "null" or "none" for null encapsulation, and
741 "LLC/SNAP", "LLC", or "SNAP" for LLC/SNAP encapsulation,
743 \fIIP\fP specifies that the owner of the PVC is IP.
745 \fI<netif>\fP specifies the network interface which the PVC is
746 to be associated with.
747 The network interface must exist and be associated with the
748 specified physical interface,
750 \fI<host> | dynamic\fP gives the address of the host at
751 the far end of the PVC, or the word "dynamic" if its address
752 is to be determined with Inverse ARP.
753 If "dynamic" is specified, LLC/SNAP encapsulation must also
756 This command creates a PVC with the specified attributes and attaches
759 \fIatm delete ARP [<netif>] <host>\fP
764 \fI<netif>\fP is the optional name of the network interface the
765 ATMARP entry is associated with.
766 If no name is specified, the specified host is deleted from the
767 cache regardless of what network interface it is associated with.
769 \fI<host>\fP is the host name or IP address of the host to
770 be deleted from the ATMARP table.
772 This command deletes the specified host's entry from the ATMARP table.
774 \fIatm set arpserver <netif> <ATM address> | local [<IP prefix> ...]\fP
779 \fI<netif>\fP specifies the network interface for which the
780 ATMARP server address is to be set.
782 \fI<ATM address>\fP specifies the ATM address of the host which is to
783 provide ATMARP service.
784 If "local" is specified instead of an ATM address, the host on
785 which the command is issued will become the ATMARP server.
787 \fI<IP prefix> ...\fP is an optional list of IP prefixes
788 that the ATMARP server will provide information about.
789 An IP prefix is specified as a dotted decimal IP address, followed by
790 a slash, followed a number specifying how many bits of the IP address
792 For example, 10.0.0.0/8 indicates that the ATMARP server will provide
793 services for all addresses on IP network 10.
794 The IP subnetwork which the network interface belongs to is
795 automatically included.
798 This command sets the address of the ATMARP server for a network
801 .I atm show ARP [<host>]
803 displays the following information:
806 \- the network interface which traffic for the entry will use.
809 \- flags showing whether the entry is valid and whether it is
811 \- flags giving further information about the ATMARP entry.
812 The meanings of the characters in the flags are:
815 P - the entry is permanent
817 R - the entry has been refreshed
819 V - the entry is valid
823 \- the number of minutes for which the entry will remain valid.
826 \- the source of the ATMARP entry.
830 LOCAL\ ----\ The entry is for an interface on the host.
832 PERM\ -----\ The entry is permanent.
833 This is used for entries that are created with the
834 \fIadd ARP\fP command.
836 REG\ ------\ The entry was created as the result of a host
837 registering with the ATMARP server.
839 SCSP\ -----\ The entry was learned via SCSP.
841 LOOKUP\ ---\ The entry was created as the result of a host
842 performing an ATMARP lookup.
844 PEER_RSP\ -\ The entry was created as the result of a host
845 answering an InARP Request.
847 PEER_REQ\ -\ The entry was created as the result of a host
848 sending an InARP Request.
852 \- the ATM address of the host the entry refers to.
855 \- the IP address or domain name of the host the entry refers to.
857 If no parameters are specified on the \fIshow ARP\fP subcommand,
858 the whole ATMARP table will be displayed.
859 If a host name or IP address is specified, only information about the
860 given host is displayed.
862 This command displays both information that has been learned dynamically
863 (through one form or another of ATMARP and via SCSP) and information
864 which has been configured by the user (through the \fIadd ARP\fP
867 .I atm show arpserver [<netif>]
869 displays the following information:
872 \- the network interface for which information is being displayed.
875 \- the state of the connection to the ATMARP server.
879 NOT_CONF\ -\ No ATMARP server has been configured for the interface.
881 SERVER\ ---\ The host is the ATMARP server.
883 PEND_ADR\ -\ No ATM address has been set for the interface.
885 POPEN\ ----\ The host is attempting to open a VCC to the ATMARP server.
887 REGISTER\ -\ The host has a VCC open to the ATMARP server and is in
888 the process of registering with the server.
890 ACTIVE\ ---\ The ATMARP server connection is active.
894 \- the ATM address of the ATMARP server.
896 If no parameters are specified on the \fIshow arpserver\fP subcommand,
897 the ATMARP servers for all network interfaces will be displayed.
898 If an interface name is specified, only information about the given
899 network interface is displayed.
901 .I atm show IPVCC [<host> | <netif>]
903 displays the following information:
906 \- the name of the network interface at which the VCC terminates.
909 \- the Virtual Path Identifier (VPI) for the VCC.
912 \- the Virtual Channel Identifier (VCI) for the VCC.
915 \- the state of the VCC.
919 PMAP\ ----\ The host has an IP packet to send and is waiting for
922 POPEN\ ---\ The VCC is being opened.
924 PACCEPT\ -\ A VCC from a remote host is being accepted.
926 ACTPENT\ -\ A PVC is open, but no ATMARP information is
927 available for it yet.
929 ACTIVE\ --\ The VCC is active.
933 \- flags giving further information about the VCC.
934 The meanings of the characters in the flags are:
937 S - the VCC is an SVC
941 L - the VCC uses LLC/SNAP encapsulation
943 M - the IP-to-ATM address mapping for the VCC is valid
945 N - there is no idle timeout for the VCC
949 \- the name and IP address of the host at the remote end of the VCC.
951 If no parameters are specified on the \fIshow IPVCC\fP subcommand, all
952 active VCCs are displayed.
953 If a host name is specified, the active VCC(s) for the given
955 If a network interface name is specified, the active VCC(s) for the
956 given network interface are displayed.
958 .SS Miscellaneous Subcommands:
961 displays a synopsis of the atm command with its subcommands
962 and their parameters.
965 displays the version of the running HARP software.
968 \fIilmid\fP (8); \fIscspd\fP (8); \fIatmarpd\fP (8).
971 Care must be taken to avoid confusing physical interfaces and
974 Please report any bugs to harp-bugs@magic.net.
977 Copyright (c) 1994-1998, Network Computing Services, Inc.
980 John Cavanaugh, Network Computing Services, Inc.
982 Mike Spengler, Network Computing Services, Inc.
984 Joe Thomas, Network Computing Services, Inc.
987 This software was developed with the support of the Defense
988 Advanced Research Projects Agency (DARPA).