1. Manuals
  2. Brands
  3. Atlantis Land Manuals
  4. Network Router
  5. I-Storm A02-RA(Atmos)_ME01
  6. Command reference manual

Atlantis Land I-Storm A02-RA(Atmos)_ME01 Command Reference Manual

Atlantis i-storm adsl router commands reference guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
I-Storm ADSL Router
Console

Commands Reference

Manual
(v1.01)
A02-RA(Atmos)_ME01

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the I-Storm A02-RA(Atmos)_ME01 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Atlantis Land I-Storm A02-RA(Atmos)_ME01

Summary of Contents for Atlantis Land I-Storm A02-RA(Atmos)_ME01

  • Page 1: Commands Reference

    I-Storm ADSL Router Console Commands Reference Manual (v1.01) A02-RA(Atmos)_ME01...

  • Page 2: Table Of Contents

    Contents 1. About this Guide 1.1 Introduction 1.2 Scope 1.3 Typographical conventions 2. ATMOS Console commands 2.1 General notes 2.2 event 2.3 restart 2.4 uptime 2.5 version 2.6 <process>, <process> <command> 2.7 . (history mechanism) 2.8 @ commands 2.9 Special-purpose commands 2.10 list 2.11 echo 2.12 tell <process>...
  • Page 3 3.4 ethertype 3.5 filter 3.6 filterage 3.7 flush 3.8 info 3.9 interface 3.10 portfilter 3.11 spanning 3.12 status 3.13 version 4. BUN Console commands 4.1 Introduction 4.2 help 4.3 version 4.4 build 4.5 config 4.6 list config 4.7 list devices 4.8 show device 4.9 list classes 4.10 show class...
  • Page 4 6.1 config 6.2 help 6.3 pool 6.4 reset 6.5 status 6.6 trace 6.7 version 7. NAT Console commands 91 7.1 event 7.2 help 7.3 interfaces 7.4 inbound 7.5 info 7.6 protocol 7.7 sessions 7.8 stats 7.9 version 7.10 dump 7.11 fragments 7.12 hashtable 8.
  • Page 5 8.18 <channel> qos 8.19 <channel> remoteip 8.20 <channel> svc 8.21 <channel> theylogin 8.22 <channel> tunnel <n> <tunnel protocol> <dial direction> 8.23 <channel> welogin 8.24 bcp 8.25 interface <n> localip 8.26 interface <n> stats 8.27 user 8.28 version 9. PPTP Console commands 9.1 Console object types 9.2 bind 9.3 <tunnel>...
  • Page 6 10.16 ipatm abort 10.17 ipatm arp 10.18 ipatm arpserver 10.19 ipatm files 10.20 ipatm help 10.21 ipatm lifetime 10.22 ipatm pvc 10.23 iphostname 10.24 nat 10.25 noerrors 10.26 norelay 10.27 ping 10.28 portname 10.29 protocols 10.30 relay 10.31 restart 10.32 rip accept 10.33 rip allowed 10.34 rip boot 10.35 rip help...
  • Page 7 10.54 ? 11. TFTP Console commands 11.1 connect 11.2 get 11.3 help 11.4 init 11.5 list 11.6 put 11.7 trace 11.8 version Index...

  • Page 8: About This Guide

    1. About this Guide 1.1 Introduction This document is a reference guide for professional user to handle ADSL modem well. It describes the command line interface (CLI) with examples. 1.2 Scope Commands for legacy drivers (eg. ATM and Ethernet drivers) are not included here. 1.3 Typographical conventions Throughout this guide, the following typographical conventions are used to denote important information.
  • Page 9 equipment, including safety information.

  • Page 10: General Notes

    2. Console and Telnet commands 2.1 General notes Apart from the chips commands, the commands are supported by the standard console. Example output is shown only to clarify the description of the commands; the actual output is not necessarily in exactly the same format. 2.2 event …...

  • Page 11: Version

    2.4.1 Syntax uptime 2.4.2 Description Displays the time for which the system has been up. 2.5 version 2.5.1 Syntax version 2.5.2 Description Displays the system type and version. 2.6 <process>, <process> <command> 2.6.1 Syntax <process> <command> <process> home home <command> 2.6.2 Description In these commands, <process>...

  • Page 12: (History Mechanism)

    ls - list ISFS files rm <file> - remove file from ISFS cat <file> - show file contents version - displays version number Use “home” to return to “mymachine>” prompt mymachine isfs> home mymachine> When the console is at the prompt of a particular process, the command home <command>...

  • Page 13: Commands

    2.8 @ commands 2.8.1 Syntax @@<line> @ <line> @<process> <line> @<process> 2.8.2 Description Lines beginning with the @ character are intercepted by the console even when the console device is bound to a file. To bypass this interception and pass a line beginning with @ to a process, the @ must be doubled;...

  • Page 14: List

    2.10 list 2.10.1 Syntax list 2.10.2 Description The list command lists the active console devices (referred to as threads) and files. For each console device, if it is bound to a file then the list shows which file it is bound to;...

  • Page 15: Exit, Exit

    2.12.1 Syntax tell <process> <command> 2.12.2 Description Sends the command as a TELL message to a specific process. Note that for many processes the tell can be omitted. 2.12.3 Example mymachine> tell hswctrl portinfo a1 port type vers flags A1 25Mbps 1QUA mast uni30 ilmi netside tx8khz manconfig 2.13 exit, exit! 2.13.1 Syntax exit...

  • Page 16: Bind , Unbind

    2.16 bind <process>, unbind 2.16.1 Syntax bind <process> unbind 2.16.2 Description The former command binds this console device to the specified process – that is, binds this device to the file, if any, opened for read by that process, and binds every file opened by the process to this device.

  • Page 17: Help

    Exits from ATMOS to the boot ROM. Note - This command is now deprecated and provides no useful output. 2.21 help 2.21.1 Syntax help help <command> 2.21.2 Description The help command lists all chips commands. ? is a synonym for this command; help <command>...

  • Page 18: Steal

    Reads the byte (rb), word (rw) or half-word (rh) at a specified address, or writes a specified value to the byte (wb), word (ww) or half-word (wh). Addresses and values are specified in hexadecimal, with an optional 0x prefix. 2.24.3 Example >...
  • Page 19 console tell command.)

  • Page 20: Bridge Console Commands

    3. Bridge Console commands 3.1 device add 3.1.1 Syntax device add <device> 3.1.2 Description This command adds a device to the bridge configuration. Attempts to add the bridge itself or an existing device to the bridge are rejected. Attempts to add devices which don’t support the Cyan interface are rejected. There is a limit on the number of devices that can be attached to the bridge.

  • Page 21: Device Delete

    attribute promiscuous selects the promiscuity behaviour of the driver. The driver requires, at configuration time, to be layered with the BUN utopia and nec98408 devices, in order to be used. So, for the sake of the following examples, let's assume that the related BUN port is called rfc_port, and it has been configured in the following way: device: rfc_dev = rfc1483, nec98408, utopia port : rfc_port = rfc_dev/PhysicalPort=0/PortSpeed=59111...

  • Page 22: Ethertype

    This command lists all the devices that are currently attached to the bridge. It does not show the stored configuration (which can be seen with the config print command). 3.3.3 Example device list 3.3.4 See also device add on page 36 and 3.4 ethertype 3.4.1 Syntax ethertype [<port>...

  • Page 23: Filterage

    started. Creation failures occur when there is no room left in the filter table for a new entry. 3.5.3 Example filter 3.6 filterage 3.6.1 Syntax filterage [<age>] 3.6.2 Description This command sets, or displays if no arguments are given, the filter table ageing time. The ageing time is the time after which MAC addresses are removed from the filter table when there has been no activity.

  • Page 24: Interface

    command is a synonym for this command. 3.8.3 Example info 3.9 interface 3.9.1 Syntax interface [sub-command] 3.9.2 Description This command accesses the ethernet support library sub-commands for the bridge itself, not for the devices which are attached to it. It is not described here. 3.9.3 Example interface stats 3.10 portfilter...

  • Page 25: Spanning

    If no arguments are given, the current settings for each port are displayed. 3.10.3 Example 1 portfilter 2 3 4 5 portfilter 3 1 3.10.4 Example 2: portfilter 2 all portfilter 3 all 3.11 spanning 3.11.1 Syntax spanning [sub-command] 3.11.2 Description The spanning tree commands are only available if it has been compiled in to the bridge.
  • Page 26 version...

  • Page 27: Bun Console Commands

    4. BUN Console commands 4.1 Introduction 4.1.1 Scope A description is provided of the use of console commands. No information on implementing additional commands is given in this chapter: implementers of new BUN devices may provide access to diagnostic or status information by implementing attributes to handle these tasks.
  • Page 28 explicit (ie.: from a device: configuration request). Device names may contain upper or lower case letters, but use case insensitive matching. portname The name of a port. This can take several forms: • The name given on the port configuration request •...

  • Page 29: Help

    For example: set port atm/usercomment="This is a comment string" set port atm/usercommand=<An alternative syntax> Within either form of quoted section, the corresponding close quote character may be embedded by prefixing with a backslash. So you could write: set port atm/usercomment=<This is a "cell based" port> set port atm/usercomment="This is a \"cell based\"...

  • Page 30: Config

    4.4.1 Syntax build 4.4.2 Description Display information about compile-time build options. For example, if tracing or debug code has been compiled into the image. 4.4.3 Example build 4.5 config 4.5.1 Syntax config <configurationstring> 4.5.2 Description Issue a configuration request to BUN. This command can be used to pass arbitrary configuration strings to BUN, effectively calling bun_ConfigMakeRequest() with the supplied configuration string.

  • Page 31: List Devices

    Each request is displayed together with any relevant information. In the case of failed requests, an error code is given and the point at which parsing of the configuration string failed is highlighted. Stalled requests can be unblocked by creating a new device with suitable properties by using the BUN config console command to issue a device configuration request.

  • Page 32: List Classes

    The device list shows which driver code is invoked by this device. For a compiled in device, this will just be the device itself. For a compound device, this will be the list of devices linked to form the compound driver. 4.8.3 Example show device utopia show device atm25...

  • Page 33: Show Port

    4.12 show port 4.12.1 Syntax port <portname> 4.12.2 Description Display detailed information about a port. This command enumerates all attributes for a port and displays them on the console. It is useful to determine the properties of a port. 4.12.3 Example port atm 4.13 set port 4.13.1 Syntax...

  • Page 34: List All Open Channels

    4.15 list all open channels 4.15.1 Syntax list all open channels [<portname> ] 4.15.2 Description This command is similar to the list channels command. The list channels command shows channels which are either enabled or open. The list all open channels command only shows channels which are open.

  • Page 35: Reset Port

    effect of any changes will be device dependent. Use this command with extreme caution. The same warnings about an application closing and reopening a channel handle apply as they do for the show channel command. Also beware that the application will not be explicitly notified of any changes made, though if it queries its own attribute data it will pick up any changes that have been made.

  • Page 36: Dhcp-Client Console Commands

    5. DHCP-client Console commands 5.1 config 5.1.1 Syntax dhcpclient config 5.1.2 Description This command displays the current configuration of the DHCP client, including selected DHCP options. 5.1.3 Example bd3000> dhcpclient config DHCP client configuration file: ‘//isfs/dhclient.conf’ timeout 60; retry 60; reboot 10;...

  • Page 37: Pool

    trace 5.3 pool 5.3.1 Syntax dhcpclient pool [verbose] 5.3.2 Description This command displays the state of the memory pool being used by the DHCP client. Should the client ever run out of memory, use of this command is helpful in determining the optimum memory pool size for the client.

  • Page 38: Trace

    ----------+-----------------+----------------+-----------------+----------- *ACTIVE* | 192.168.219.151 | 192.168.219.1 | --------------------------------------------------------------------------- 5.5 trace 5.5.1 Syntax dhcpclient trace <trace option> 5.5.2 Description This command enables or disables tracing for the DHCP client. If no arguments are given the command lists the current tracing options enabled. The following trace options are available: Option lease...
  • Page 39 5.7.2 Description The ip device add command adds an interface to the configuration of the IP stack. The last parameter of the command would normally the IP address of the interface; use of the string dhcp causes the IP address to be discovered by the DHCP client software.

  • Page 40: Dhcp-Server Console Commands

    6. DHCP-server Console commands This chapter describes the DHCP-server Console commands.

  • Page 41: Config

    6.1 config 6.1.1 Syntax dhcpserver config [add <text>|confirm|delete|flush] 6.1.2 Description This command displays or edits the current configuration of the DHCP server. To display current configuration, provide no arguments to the command. • Use o f the add option adds the line <text> to the configuration file. •...

  • Page 42: Help

    6.2 help 6.2.1 Syntax dhcpserver help <command|all> 6.2.2 Description This command provides help on the various console commands provided by the ATMOS DHCP server. Specifying a command name gives detailed help on the command. Specifying all gives detailed help on all available commands. 6.2.3 Example bd3000>...

  • Page 43: Status

    dhcpserver reset 6.4.2 Description This command prompts the server to do a warm reset of itself. This has the effect of bringing the server back up as if the system had been rebooted, except that the lease database is preserved in SDRAM between resets. Please note, however, you should still save the configuration file to FLASH if you want the configuration to be preserved upon rebooting the whole system.

  • Page 44: Trace

    192.168.219.8 192.168.219.9 192.168.219.10 | 6.6 trace 6.6.1 Syntax dhcpserver trace <trace option> 6.6.2 Description This command enables or disables tracing for the DHCP server. If no arguments are given, the command lists the current tracing options enabled. The following trace options are available: Option lease bootp...

  • Page 45: Nat Console Commands

    7. NAT Console commands...

  • Page 46: Event

    This chapter describes the NAT (Network Address Translation) Console commands. 7.1 event 7.1.1 Syntax nat event [n]...

  • Page 47: Help

    7.1.2 Description This command displays or sets the current level of event tracing in the NAT process. Larger values of n result in more verbose trace output. For example: Event level All trace messages are printed as background output, and therefore will not be displayed asynchronously on the console unless the event show command has been issued.

  • Page 48: Inbound

    Name Status Ethernet enabled pppnot ready 7.4 inbound 7.4.1 Syntax nat inbound list nat inbound add <i/f> <port>/<proto> <new IP> [quiet] nat inbound delete <#> nat inbound flush 7.4.2 Description This command enables the user to list or to set up a series of rules, to determine what happens to incoming traffic.

  • Page 49: Info

    r1483 21/tcp bd3000> nat inbound delete 2 7.5 info 7.5.1 Syntax nat info 7.5.2 Description This command displays the values of various parameters which are defined in the module file, for example the session table size and the session timeouts. NAT’s current memory usage is also displayed.

  • Page 50: Sessions

    7.6.3 Example bd3000> nat protocols Name Port/IP protocol 21/tcp 7.7 sessions 7.7.1 Syntax nat sessions <i/f> [all | summary] 7.7.2 Description The nat sessions command displays a list of currently active NAT sessions on the interface <i/f>. In this context, a session is a pair of source IP addresses and port numbers (and corresponding new port number) that NAT regards as one side of an active connection.

  • Page 51: Version

    The nat stats command does not provide the total number of packets or bytes transferred, as this information is normally available from the device driver on the interface which NAT is filtering. 7.8.3 Example bd3000> nat stats ethernet Outgoing TCP sessions created: 456 Outgoing UDP sessions created: 123 Outgoing ICMP query sessions: Outgoing ICMP errors:...

  • Page 52: Hashtable

    nat fragments <i/f name> 7.11.2 Description This command is only available in debug builds. nat fragments prints information on the queues in which NAT holds fragmented IP datagrams, displaying the IP datagram identifier, the number of fragments queued and a NAT session pointer for each queue. This command is provided for debug purposes only.

  • Page 53: Console Object Types

    8.1 Console object types The ppp process presents its setup in terms of a number of distinct object types: • The upper limit on the number of each of these objects permitted in a system is configured using the config resource console command. •...
  • Page 54 pvccreate a1 32 a1 33 (at the switch console, if it is a Virata Switch) ppp event 5 (at the console of the PPP ATMOS system) ppp 1 pvc 32 ppp 2 pvc 33 ppp 1 enable ppp 2 enable (they should now swap packets and synchronise) ppp 1 status This should show that the two ends are connected.

  • Page 55: Channel> Clear

    ppp 2 remoteip 192.168.200.2 ppp 2 enable (and the corresponding setup for each of the channels 3 to 8 as well) Clients can now dial in to this server, be allocated IP addresses and traffic will be sent to and from the router. 8.2.4 Remote Bridging To create a system where two bridges are connected by a PVC, do the following at each end: (In this example, interface 2 is attached to the bridge in ATMOS (interface...

  • Page 56: Channel> Echo

    8.5.1 Syntax <channel> discard [<size>] 8.5.2 Description Discard is a PPP LCP packet type, which is like the Echo packet type but does not generate a return. This can be used for more careful tests of data transfer on the link, for instance at sizes near the negotiated MRU.

  • Page 57: Channel> Enable

    8.8 <channel> enable 8.8.1 Syntax <channel> enable 8.8.2 Description Set the enable flag for a PPP channel. By default, this is disabled. In the PPP state machine, this flag sets the PPP link to open. If it is already open, there is no effect.

  • Page 58: Channel> Info

    Learning occurs in this direction only. Setting hdlc to 0 clears this learned state. Configuration saving does not save the learned state. 8.11 <channel> info 8.11.1 Syntax <channel> info [all] 8.11.2 Description Provide information about the current settings of this channel. This includes all configured state, and also current protocol information.

  • Page 59: Channel> Lcpmaxterminate

    8.14.1 Syntax <channel> lcpmaxfailure [<n>] 8.14.2 Description Set the Max-Failure parameter for LCP, as described in Section 4.6 of RFC1661. This is the maximum number of consecutive Configure Naks that will be sent before assuming that parameter negotiation is not converging. Call with no argument to find the current setting.

  • Page 60: Channel> Pvc

    8.17 <channel> pvc 8.17.1 Syntax <channel> pvc [[<port>] <vpi>] <vci> [ip|mac] [listen] <channel> pvc none 8.17.2 Description Attach an ATM PVC to the given PPP channel. The port can be specified (only for a multi-port device), and the VPI (default is 0), and the VCI. The allowable range of port, VPI, VCI depends on the ATM driver.

  • Page 61: Channel> Qos

    8.18 <channel> qos 8.18.1 Syntax <channel> qos [cbr|ubr] [pcr <pcr-tx> [<pcr-rx>]] 8.18.2 Description Specify that the VC for a PPP channel should be Constant Bit Rate or Unspecified Bit Rate, and (optionally for UBR) give a Peak Cell Rate for the connection. If two values are specified then they are the transmit and receive PCRs respectively.

  • Page 62: Channel> Theylogin

    Specify that the VC for a PPP channel should be an SVC (i.e. created by signalling). This can either be by listening for an incoming call, or by making an outgoing call to a specified ATM address. The outgoing call or listen occurs immediately. If the call fails it will be retried after a few seconds.

  • Page 63: Channel> Tunnel

    This command specifies that when using this channel, the user must log on using the specified protocol, and that they must provide any name/password combination which has been defined for that protocol, using the user command. To remove this information on a channel, call theylogin with a single argument of none.
  • Page 64 8.24.1 Syntax bcp stp|nostp 8.24.2 Description This command describes parameters for BCP, the Bridge Control Protocol, which is used to transport MAC (Ethernet) packets over the PPP link. See the section entitled Standards Conformance DO-007078-PS for a definition of the BCP option settings which are not controllable.

  • Page 65: Console Commands

    can be attached to the bridge or router, like other Ethernet devices in ATMOS. It also provides an ifEntry to SNMP providing basic information about traffic through the interface. This command shows the basic information about byte and packet traffic through the interface, in SNMP terms.
  • Page 66 9.1 Console object types The PPTP process provides a number of PPTP connection tunnels. A tunnel consists of a control connection between the local PAC and a PNS, and a data connection (known as a call) through which a number of PPP connections or channels may be multiplexed. The upper limits of several parameters may be configured using the config resource console command.

  • Page 67: Bind

    The rest of this section details the individual console commands provided. 9.2 bind 9.2.1 Syntax: bind <ipaddress>|any|none 9.2.2 Description: Specify which local interface to bind a listener to for incoming control connections. If ipaddress is specified, PPTP will listen on port 1723 on that interface only for incoming control connections.

  • Page 68: Tunnel> Create

    produce an error message. 9.4 <tunnel> create 9.4.1 Syntax <tunnel> create <ipaddress>|listen 9.4.2 Description: Create a tunnel object. If ipaddress is specified, the tunnel is associated with a remote PNS at that IP address. The control connection is not actually established until use of the tunnel is requested by PPP, or an explicit connect is issued.

  • Page 69: Tunnel> Event

    9.6.2 Description Explicitly disconnect a tunnel (the opposite of connect). All data connections across the tunnel are terminated and the control connection is closed. If the tunnel object is associated with a particular remote PNS (as created with <tunnel> create <ipaddress>), it may be reconnected later, either explicitly with another connect command, or implicitly by PPP requesting to use it.

  • Page 70: Version

    9.9.1 Syntax list 9.9.2 Description Lists all currently created tunnel objects and the IP address of the remote PNS associated with each one. 9.10 version 9.10.1 Syntax version 9.10.2 Description Provide the version number for the source of the pptp process. 10.TCP/IP Console commands This chapter describes the TCP/IP Console commands.

  • Page 71: Abort

    The table below shows the commands that can be issued to the IP process in TELL messages or on the console to its stdin stream (after typing @ip, for example). It shows which are mentioned in the ip help output, and which set some configuration that is saved in flash memory.
  • Page 72 uptime version The key for the above table is shown below: Symbol ● — May be inserted explicitly in //isfs/resolve (Eg. for debugging purposes), but not saved by ipconfig save. Two obsolescent commands are not shown in the table above nor in the fuller descriptions below;...
  • Page 73 mymachine> ip abort 3 10.3 arp 10.3.1 Syntax arp add <i/f> <IP address> <MAC address> arp delete <i/f> <IP address> arp flush arp [list] arp help [all|<cmd>] 10.3.2 Description Allows display and manipulation of the ARP table: the list of IP addresses and corresponding MAC addresses obtained by ARP (see the ATMOS TCP/IP Functional Specification, DO-007285-PS) on Ethernet-like interfaces.
  • Page 74 arp add ether 192.168.50.1 arp add ether 192.168.50.57 00:20:af:2e:fa:3c # 3m13s mymachine> ip arp flush mymachine> ip arp # flane ARP table is empty # ether ARP table is empty mymachine> ip arp arp add flane 192.168.2.108 00:20:2b:03:0a:72 # 10m58s # ether ARP table is empty (The last example shows that the MAC address for 192.168.2.108 has been automatically added again, having been discovered by means of the ARP protocol.)
  • Page 75 device ether ether device loop loop mymachine> ip ping 127.0.0.1 ip: ping - reply received from 127.0.0.1 mymachine> ip ping 192.168.2.1 ip: ping - transmit error: Host is down (rc=62) mymachine> ip autoloop on mymachine> ip ping 192.168.2.1 ip: ping - reply received from 192.168.2.1 10.6 config 10.6.1 Syntax config [save]...
  • Page 76 snmp 161/UDP tftp 69/UDP telnet 23/TCP mymachine> ip config save Updating flash filing system ... done ip: configuration saved 10.7 device 10.7.1 Syntax device [list] device add <i/f> <type> [<file>] [mtu <size>] [<IP address>] device delete <i/f> device flush 10.7.2 Description Displays the interfaces that IP is configured to use (device list), or adds an interface to the configuration (device add), or deletes an interface (device delete), or deletes all interfaces (device flush), from the configuration.
  • Page 77 config.h ETHERNET_DEVICE_NAME “s//edd” If a default file is not defined, the name ether is not supported. However, it is still possible to define devices of type ether with an explicit filename. The class IP-over-ATM includes both SVC-based and PVC-based IP-over-ATM; the decision whether to use SVCs or PVCs is made at initialization, by testing the interface colors of the file if it supports the Indigo interface, then SVCs are used, and otherwise PVCs.
  • Page 78 setting means that the IP address should be learned by DHCP. For example: ip device add ether ether dhcp Note that DHCP is not supported on all interface types. For more information, refer to ip device on page 80. If the IP process is given a command line (a little-used feature of ATMOS!) then each argument will be treated as a possible Ethernet-like file to open, given names ether1, ether2, and so on.
  • Page 79 device ether ether //edd mtu 1500 192.168.2.1 device flane ether //lec1 mtu 1500 192.168.55.1 # DISABLED 10.9 enable 10.9.1 Syntax enable [<i/f> [mtu <size>] [<IP address>]] 10.9.2 Description Enables all interfaces, or just a specified interface. Can also be used to set the MTU and IP address on an interface when enabling it (or change them on an interface that is already enabled);...
  • Page 80 The etherfiles command is hidden, not shown by ip help. 10.11.3Example mymachine> ip etherfiles ether: //edd flane: //lec1 atm: (no ethernet device) 10.12 files 10.12.1Syntax files [full] files <assoc> 10.12.2Description Lists the files (associations) that other applications (or, internally, RIP) have opened on //ip.
  • Page 81 //ip/TYPE=UDP/LPORT=69/TIMEOUT_CONX=1000/TIMEOUT_LISTEN=0/TIMEOUT_IDLE=0/RETRY_CONX=2/TOS =routine/DELAY=normal/THROUGHPUT=normal/RELIABILITY=normal/BUFFERRX=off/BUFFER_TXSIZE=-1/ BUFFER_RXSIZE=-1/FRAGMENT=on/TTL=60/OPTIONS=off/CHECKSUM=on/TIMEOUT_USER=540000 10.13 flush 10.13.1Syntax flush <assoc> 10.13.2Description Given an association number (see association, this does a TCP push (see RFC 793), which, roughly speaking, causes the data sent so far to be delivered as quickly as possible to the recipient, without waiting to be buffered with subsequent data.

  • Page 82: Ipatm Abort

    Commands are: disable enable norelay route stats subnet ‘.’ repeats the last command Type "ip help all" or "ip help <command>" for more details mymachine> ip help arp arp Syntax arp <cmd> arp help 10.16 ipatm abort 10.16.1Syntax ipatm abort <n> 10.16.2Description Closes an IP-over-ATM SVC;...

  • Page 83: Ipatm Files

    10.18.1Syntax ipatm arpserver [<i/f> [<ATM address>|here]] 10.18.2Description Displays or sets the ATMARP server used for an interface, which must be an IP-over-ATM interface using SVCs. The interface name is optional when displaying: if omitted, the ATMARP servers for all such interfaces are listed. (Since currently there can only be one such interface, this behaviour is present only for possible consistency with future versions.) The parameter here causes no ATMARP server to be used;...

  • Page 84: Ipatm Help

    6: on atm Idle 7: on atm Idle 8: on atm Idle 9: on atm Idle 10: on atm Idle 10.20 ipatm help 10.20.1Syntax ipatm help [<cmd>|all] 10.20.2Description Displays help on ipatm subcommands. 10.20.3Example mymachine> ip ipatm help Commands are: abort arp files help lifetime pvc...

  • Page 85: Ipatm Pvc

    mymachine> ip ipatm lifetime 90 Idle lifetime for connections: 1m30s 10.22 ipatm pvc 10.22.1Syntax ipatm pvc ipatm pvc add <i/f> <port> [<vpi>/]<vci> [pcr <pcr>] [remoteip <IP address>] ipatm pvc delete <port> [<vpi>/]<vci> ipatm pvc flush 10.22.2Description The table below describes the use of each of the four commands given above: Command ipatm pvc ipatm pvc add...

  • Page 86: Iphostname

    myswitch> ip ipatm pvc add ipoa b1 61 pcr 50000 myswitch> ip ipatm pvc add ipoa b1 62 remoteip 192.168.4.32 myswitch> ip ipatm pvc ipatm pvc ipoa a3 0/60 pcr 60000 ipatm pvc ipoa b1 0/61 pcr 50000 ipatm pvc ipoa b1 0/62 pcr 60000 remoteip 192.168.4.32 10.23 iphostname 10.23.1Syntax iphostname add <IP address>...

  • Page 87: Noerrors

    nat: Interface “ether” now enabled nat: Interface “ether” IP address is 192.168.200.90 bd3000>ip nat delete ether nat: Interface “ether” deleted by IP 10.25 noerrors 10.25.1Syntax noerrors 10.25.2Description Undoes the effect of the errors command; equivalent to untrace errors. The noerrors command is hidden, not shown by ip help. 10.25.3Example mymachine>...

  • Page 88: Portname

    10.27.2Description Sends an ICMP Echo message to the specified IP address. • <ttl> (default 30) is the TTL (time-to-live) to use. A crude traceroute functionality can be obtained by repeating the ping. command with increasing TTL values, starting with 1. •...

  • Page 89: Protocols

    provided the protocol type (UDP or TCP) is appropriate. They are also displayed in place of port numbers, when a suitable mapping exists. The Damson interface (described in the ATMOS TCP/IP Functional Specification, DO-007285-PS) allows other processes to query the mapping. <protocol>...

  • Page 90: Relay

    10.30 relay 10.30.1Syntax relay relay all | <i/f> [<i/f>] [forward] 10.30.2Description Displays or sets what forwarding ATMOS TCP/IP will do between interfaces. The combinations of setting forwarding can be a bit confusing; they behave as follows: Command relay all relay if1 relay if1 forward relay if1 if2 relay if1 if2 forward...

  • Page 91: Rip Accept

    10.31.1Syntax restart 10.31.2Description Reboots the system. This command is deprecated. To reboot the system, use the restart command from the ATMOS console. 10.31.3Example mymachine> ip restart 10.32 rip accept 10.32.1Syntax rip accept [all|<i/f>] [none|<version>*] 10.32.2Description Controls for which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) ATMOS TCP/IP will accept incoming information on each interface.

  • Page 92: Rip Boot

    mymachine> ip rip allowed rip send ether 2 rip send flane 2 rip accept ether 1 2 rip accept flane 1 2 10.34 rip boot 10.34.1Syntax rip boot 10.34.2Description Broadcasts a request for RIP information from other machines. ATMOS TCP/IP does this automatically when it first starts up, and the routing information should be kept up to date by regular broadcasts from the other machines, so this command is normally of little use.

  • Page 93: Rip Hostroutes

    10.36 rip hostroutes 10.36.1Syntax rip hostroutes [off] 10.36.2Description Sets or clears the hostroutes flag; ATMOS TCP/IP will accept RIP routes to individual hosts only if this flag is on. If the flag is off, then RIP version 1 routes that appear to be to individual hosts will be treated as if they were to the network containing the host;...

  • Page 94: Rip Relay

    mymachine> ip rip poison 10.39 rip relay 10.39.1Syntax rip relay <RIP version> <name> [<i/f> [<timeout>]] 10.39.2Description Configures a RIP relay. RIP relays were designed as a means of using RIP on a non-broadcast medium (currently, only IP-over-ATM); on such an interface, ATMOS TCP/IP will send RIP information individually to each configured RIP relay, instead of broadcasting it.

  • Page 95: Rip Trigger

    rip send [all|<i/f>] [none|<version>*] 10.42.2Description Controls which version or versions of RIP (RIP version 1, RFC 1058, or RIP version 2, RFC 1723) ATMOS TCP/IP will use to broadcast routing information on each interface. If both versions are specified, routing information is broadcast in duplicate, once using each version.
  • Page 96 • <name> is an arbitrary name specified to route add that can be used to delete the route using route delete. • <dest> is the IP address of the network being routed to (only those bits of <dest> corresponding to bits set in <mask> are relevant). •...

  • Page 97: Routeflush

    mymachine> ip route add default 0.0.0.0 192.168.2.3 0:0:0:0 mymachine> ip route add testnet1 192.168.101.0 192.168.2.34 mymachine> ip route add testnet2 192.168.102.0 192.168.2.34 ff:ff:ff:0 1 60 mymachine> ip route route add testnet2 ether * route add testnet1 ether route add default ether 10.45 routeflush 10.45.1Syntax...

  • Page 98: Stats

    10.47.1Syntax snmp access [read|write|delete|flush] <parameters> snmp config [save] snmp help [<cmd>|all] snmp trap [add|delete|flush|list] <parameters> snmp version 10.47.2Description Manages the list of SNMP community names (also used as passwords by other applications, such as telnet) and the list of SNMP trap destinations. (See the ATMOS TCP/IP Functional Specification, DO-007285-PS for information about the interface to this information.) The syntax of the commands is documented in the ATMOS SNMP Functional...

  • Page 99: Subnet

    ip: Transmitted UDP packets: 10.49 subnet 10.49.1Syntax subnet subnet add <name> <i/f> <IP address> <mask> subnet delete <name> subnet flush 10.49.2Description Lists defined subnets; defines a subnet; deletes a subnet definition; or deletes all subnet definitions. • <name> is a label, that can be specified by subnet add and later used by subnet delete to delete the subnet.

  • Page 100: Trace

    subnet ether.home 10.50 trace 10.50.1Syntax trace [<option>] 10.50.2Description Turns on an IP tracing option, or lists the available options. Note that tracing messages are written to background output, so with the standard console one must use the event commands to see them. An option can be: •...

  • Page 101: Uptime

    untrace [<option>] 10.51.2Description Turns off IP tracing options. The syntax is the same as for trace; in particular, untrace all turns off all tracing. The trace command is hidden, not shown by ip help. 10.52 uptime 10.52.1Syntax uptime 10.52.2Description Displays the time for which the ATMOS system has been running. This command is deprecated.
  • Page 102 10.54.2Description The ? command is simply a synonym for the help command, and behaves in the same way.
  • Page 103 11.TFTP Console commands 11.1 connect 11.1.1 Syntax connect <node_name> || <ipaddr> 11.1.2 Scope: Client mode only. 11.1.3 Description The connect command is used to specify the remote host name or IP address that will be used in subsequent client mode transfers. Either a host name may be entered, searched for in the ipaddresses configuration file, or an IP address in the form abc.def.ghi.jkl.
  • Page 104 11.2.4 Example get ipaddresses 11.3 help 11.3.1 Syntax help 11.3.2 Description The help command displays the help text which lists the (commonly used) TFTP commands. The init command is not listed in the help text. The trace command has a large number of optional parameters and detail on this command may be displayed by typing trace help.
  • Page 105 11.6.1 Syntax put [local_file] <remote_file> 11.6.2 Scope: Client mode only. 11.6.3 Description The put command requests TFTP to transmit a file to the remote host previously specified using the connect command. By default, the file is named remotely as the local filename but by specifying a second filename, an implicit rename is performed.
  • Page 106 Index Symbols . (history mechanism 13 <process>, <process> <command> 11 ? (IP) 218 @ commands 14 abort (IP) 155 Adobe Acrobat 4 arp (IP) 156 arprouting (IP) 158 autoloop (IP) 159 bcp (PPP) 133 bind (PPTP) 142 bind <process> 23 build (Bun) 57 Caution symbol 3 <channel>...
  • Page 107 <channel> qos (PPP) 126 <channel> remoteip (PPP) 127 <channel> svc (PPP) 128 <channel> theylogin (PPP) 130 <channel> tunnel <n> <tunnel protocol> <dial direction> (PPP) 131 <channel> welogin (PPP) 132 channelnumber 53 class definitions 53 config (Bun) 58 config (DHCPClient) 74 config (DHCPServer) 82 config (IP) 160 conventions...
  • Page 108 Feedback 4 files (IP) 170 filter (Bridge) 41 filterage (Bridge) 42 flush (Bridge) 43 flush (IP) 171 fragments (Nat) 103 get (IP) 172 get (TFTP) 221 hashtable (Nat) 104 help 28 help (Bun) 55 help (DHCPClient) 75 help (DHCPServer) 84 help (IP) 173 help (Nat) 93 help (TFTP) 222...
  • Page 109 ipatm help (IP) 178 ipatm lifetime (IP) 179 ipatm pvc (IP) 180 iphostname (IP) 182 list 17 list (PPTP) 149 list (TFTP) 224 list all open channels (Bun) 68 list channels (Bun) 67 list classes (Bun) 62 list config (Bun) 59 list devices (Bun) 60 list ports (Bun) 64 mem 30...
  • Page 110 rb 31 relay (IP) 190 reset (DHCPServer) 86 reset port (Bun) 71 restart 8 restart (IP) 192 rh 31 rip accept (IP) 193 rip allowed (IP) 194 rip boot (IP) 195 rip help (IP) 196 rip hostroutes (IP) 197 rip killrelay (IP) 198 rip poison (IP) 199 rip relay (IP) 200 rip relays (IP) 201...
  • Page 111 status (DHCPServer) 87 steal 32 subnet (IP) 211 Symbols, used in this guide 3 tell 33 tell <process> 19 trace (DHCPClient) 78 trace (DHCPServer) 88 trace (IP) 213 trace (TFTP) 226 <tunnel> connect (PPTP) 143 <tunnel> create (PPTP) 144 <tunnel> delete (PPTP) 145 <tunnel>...
  • Page 112 Warning symbol 3 wb 31 wh 31 ww 31...

This manual is also suitable for:

I-storm a02-ra

Table of Contents

Save PDF