First Time Configuration Tour  

 

This section guides you step-by-step through the configuration pages allowing you to check the default values and change them if required.

Note: The button will take you out of the First Time Configuration Tour.

  1. Activate a Web browser on a local host on the LAN.
  2. In the URL field, type in the IP address of the IOCOMM and press . You will obtain the IOCOMM Administration page.
  3. Type in the administration password and select Confirm.
  4. On the IOCOMM Main menu page, select First time configuration tour.

The IOCOMM LAN interface page.

  1. In the IP address box, enter the IP address assigned to this IOCOMM.

    Note: The IP address may have been previously entered.

  2. In the IP Netmask box, enter the appropriate netmask value.

Note: The Ethernet address for the IOCOMM is factory set and cannot be modified.

  1. When you have completed the LAN interface page, select Submit to confirm entries or, if you have made no changes, select Skip to continue to the next page.

The IOCOMM Domain Name Service page.

Entering data in the fields is optional; you may find it useful.

Note: To avoid confusion, the name entered here should be the name which has been set up on the DNS server(s) for this device. Although you can enter a different name, it serves no purpose.

  1. Complete the following fields as required:

    First server
    Second server
    Third server
    Default domain
    IOCOMM host name
    NetBIOS name servers

  2. If you enter data select Submit, if not select Skip to continue to the next page.

The IOCOMM Static routes configuration page

You need to add a new entry for each permanent route you wish to create.

RIP listening is a more dynamic alternative to these fixed links and can be found on the next page in the First Time Configuration Tour.

To create a static route:

  1. Select Create new entry. The following fields will need to be completed.

    Destination IP

  2. Enter the IP address of the remote host to which you wish to create a static route.

    Note: You can also specify a host name in this box, but there must be a corresponding DNS entry.

    Destination mask

  3. Enter the appropriate mask value.

    Gateway IP

  4. Enter the IP address for the gateway (router) device.

    Note: You can also specify a host name in this box, but there must be a corresponding DNS entry.

  5. Select Submit. You will obtain the Static routes configuration main page and your new entry will be listed.

  6. If required, create further static routes by selecting Create new entry.

  7. If you wish to store a default route enter the IP address in the Default route field and select Submit.

    Note: You can also specify a host name in this box, but there must be a corresponding DNS entry.

  8. If you do not wish to store a default route, select Skip to continue to the next page.

The IOCOMM Dynamic routing page.

  1. Select to enable one of the three RIP options:

    Enable RIP listening only

    Enable RIP listening and advertising.

    Disable RIP

  2. Select the appropriate version of RIP

    RIP Version 1 only

    RIP Version 2

  3. Enter the RIP Version 2 authentication password (if applicable)
  4. If you enter data select Submit, if not select Skip to continue to the next page.

The IOCOMM TCP security page.

This page enables you to enter TCP security information for up to three permitted IP addresses.

  1. In the First permitted IP addresses fields, enter the Mask value and Mask result.
  2. Repeat this step for the second and third permitted IP address (as appropriate).
  3. If you enter data select Submit, if not select Skip to continue to the next page.

The IOCOMM Change Administration password page.

Note: You do not have to change the administration password from the default at this time, but if not already changed it is advisable to do so. If you do decide to change it, make sure to keep a note of the new password - it is very difficult to recover admin control without the correct password.

  1. If you enter a new password, complete the password boxes and select Submit.
  2. If you do not wish to enter a new password at this time, select Skip to continue to the next page.

The IOCOMM Network CLI service (telnetd) page.

  1. Select Enable telnetd.

    This option allows or disallows an external user to make a telnet connection to the access server.

  2. From the list below, select the authentication type you wish to impose when the user tries to establish a dial-up connection to the IOCOMM.

    Allow automatic PPP detection

    PPP uses PAP authentication

    PPP uses CHAP authentication

  3. If required, select Display login banner to enable display of the login banner (entered on the Global messages page) when a user makes a telnet connection to the IOCOMM.
  4. If required, select Display message of the day to enable display of the message of the day (entered on the Global messages page) when a user makes a telnet connection to the IOCOMM.
  5. Click the appropriate button to select the type of authentication mode for telnet connections to the CLI:

    (Disallows any access.)

    (Asks for the password.)
     
    (Allows them straight in.)


  6. Select Submit if you have entered data or Skip if no changes have been made.

The IOCOMM SNMP page

Enable SNMP access
  1. If you wish to implement SNMP, check the box.

    You have the option of entering general system information in the following fields; for example:

    Support contact

    [John_Brown]

    System description

    [Access_Server_03]

    System location

    [Accounts_Department]

    This information may be useful for general network administration. The information you enter in these fields will appear on the IOCOMM Administration page each time the Web browser for the IOCOMM is opened.

    The Support contact line can also be used to create an e-mail shortcut, enabling e-mail messages to be sent directly to the relevant support person (internally or externally). To use this facility, complete the field using the form as follows:

    Support contact

    [mailto:john.brown@anycompany.co.uk]


    The e-mail shortcut can then be used by clicking on the mail address line shown on the IOCOMM Administration page.

    Enable SNMP traps

  2. If you require SNMP traps, check the box.
  3. Enter the IP Address and Community name for up to three trap settings as required.
  4. Select Submit if you have entered data or Skip to continue to the next page.

The IOCOMM Global messages page.

The Global messages page allows you to enter any information that you feel would be relevant or useful to log-in users.

For example, the Login banner might say Welcome to the XYZ network. The Message of the day might say Network unavailable after 4pm today.

  1. Complete the text fields for Login banner and Message of the day as required.

    Note: Product I.D. and Serial number are factory pre-set and cannot be changed.

  2. If you enter data select Submit, if not select Skip to continue to the next page.

The IOCOMM Serial ports configuration page.

This page allows you to specify which port you wish to configure.

The options are:

  1. Select Physical parameters

    Description

    [Asynchronous serial device ]

    Note: The Description field is for information only and is set to Asynchronous serial device as default. It can be changed as required, but has no operational function.

    The next options allow you to specify:

    Terminal type

    [wyse50 ]

    Attached device

    [Asynchronous terminal ]

    Current mode is:

    Asynchronous

    Select new mode

    [Synchronous]

    Baud rate

    [9600 ]


    Note: The Terminal type field is for information only and is set to wyse50 as default.

  2. For Attached device and Baud rate, select the down arrow for option list and select the required settings.
  3. At this point, you can write this configuration to one or more additional ports for which you require the same settings. If required, check the additional port boxes.
  4. Select Check here to reset port and make changes immediate if you wish the new settings to be effective immediately.
  5. Select Access options.
  6. If you require the port(s) to be Available for outgoing services (e.g. dial out), check the box.

    Incoming authentication

  7. If you require PPP services, select the appropriate box(es) from the following options:

    Allow automatic PPP detection

    PPP uses PAP authentication

    PPP uses CHAP authentication

  8. If you wish the Login banner and/or the Message of the day to appear on this port, select the appropriate boxes:

    Display login banner

    Display mess age of the day

    Granted capabilities

  9. The items under Granted capabilities specify the local and remote access capability of the port(s). Select the boxes as required .

    Login (to remote host)
    This option allows the dial-in user to connect onward to other hosts via the IOCOMM using telnet or rlogin

    Framed access (PPP or SLIP connection):
    This option allows the user to run PPP or SLIP protocols over the link.

    NAS (Command Line Interface):
    This option enables access to the CLI with user level (non-admin) commands.

    Admin:
    This option enables access to the CLI with a full set of access server administration commands.

  10. Select Check here to reset port and make changes immediate if you wish the new settings to be effective immediately.

  11. Select Modem options.

    The Modem options (initialisation commands) available on this page are listed below. The entries shown to the right of each field are the default settings.

    1st init string

    [AT ]

    Response

    [OK ]

    2nd init string

    [ATV1 ]

    Response

    [OK ]

    3rd init string

    [ATS0=1 ]

    Response

    [OK ]

    Dial string

    [ATD ]

    Response

    [CONNECT ]

    Modem disconnect

    [%D+++%DATH%D ]

    Response

    [OK ]

    IOCOMM is shipped with default standard AT command settings. These default settings should work with many `standard' modem types.

  12. Edit the commands as required and then select any additional ports to which you wish to write the new configuration.

    Note: Initialisation strings should not contain any commands that may cause the modem to pause operation. For example, the save configuration command on some modems.

    Changes will not take place until port is next reset.

  13. Select Check here to reset port and make changes immediate if you wish the new settings to be effective immediately.
  14. Select Submit to continue to the next page.

The IOCOMM Event logging page.

IOCOMM can log events to the console port (A), an internal storage buffer or a remote host.

  1. These options allow you to select where the event logging is stored or displayed and the level of event log you wish to capture. Select from the pull down menus as required.

    Minimum level to log to console

    [No logging ]

    : displays on console on port A

    Minimum level to log to buffer

    [debug ]

    : stores log in internal buffer

    Minimum level to log to remote host

    [No logging ]

    : logs events in syslog on remote host

    If you select No logging, no event logs will be stored to this destination. If you select any other level, all levels including the one you have selected and above, will be logged. For example, if you select notice, all events from emergency down to notice will be logged. Repeat this selection for the three destinations.

    Note: The IOCOMM internal log holds the last 100 event logs.

    The event logs saved to buffer or console will provide time and date stamping only if a remote host has also been specified (even if No logging has been set for the remote host).

    The event logs written to the IOCOMM buffer can be viewed by using either the command syslog display [number] in CLI mode or by using the IOCOMM web browser pages (from the Main menu, select Status and statistics display, then Event logging, then System log).

    Note: If the IOCOMM is switched off or re-booted, all event logs held in the internal buffer will be lost.

  2. To write logs to a remote host, enter either the host name or IP address for the host in the Remote syslog host box. Event logs can be viewed on the selected remote host using the standard syslog command.

    Remote syslog host

    [ ]

    Remote host facility to map to

    [NONE ]


    Note: For this option to function correctly with a host name, DNS must be correctly configured. If DNS is not correctly configured, only the IP address entry can be resolved.

  3. You can set up a special facility on the remote host to capture event logs to specific locations. For example, you could select local 3 as the facility for capturing event logs from the IOCOMM in a particular location, or you could set up a log facility for each individual IOCOMM.
  4. When you have completed all required sections, select Submit to save entries or Skip to continue to the next page.

The IOCOMM RADIUS page.

IOCOMM supports RADIUS authentication and accounting.

  1. Check the following boxes as required.

    Enable RADIUS authentication

    Enable RADIUS accounting

    Enable special login prefix recognition

    Note: Without the Enable RADIUS authentication box selected, only the Enable special login prefix recognition setting will be effective.

  2. Enter the details for the First server on the network, completing the Server's host name and Shared secret boxes.

    First server

    Host name

    [ ]

    Shared secret

    [ ]

  3. You can also set the Network connection ports. To do this, select the appropriate button. The options are:

  4. Repeat the steps above, for the Second and Third servers (if required).
  5. Select Submit, or Skip to continue to the next page.

The IOCOMM Read or write configuration page.

This page allows you to copy the complete configuration information from the current IOCOMM to a file on a remote host.

  1. First create a file on the remote host; the file should have zero contents. An example is given below:

    /etc/tftpboot/access_server1.db

  2. In the Name or IP address of host field, enter the remote host IP address or host name if you specified a DNS server on the Domain Name Service page

  3. In the Configuration file name field, enter the full path and file name of the file you created on the remote host.

  4. Select Write configuration to host. The configuration will then be copied to the file on the remote host and a page similar to the following example should appear:

    Writing file /usr/tftpboot/hamlet.db
    To remote host magma
    This is the end of the first time tour.
    To make all changes effective now, please click on the Shutdown button.


  5. When the above page appears, the operation is complete. If you select Skip instead of Write configuration to host, you will be taken straight to the IOCOMM Shutdown unit page without copying the configuration.

    Note: The file can be copied back to one or more IOCOMMs to duplicate configuration information. See the section Saving / Copying Configuration File

  6. Select Shutdown to obtain the IOCOMM Shutdown unit page.

The IOCOMM Shutdown unit page.

  1. Select Confirm shutdown.

    The IOCOMM will re-boot and all changes submitted during the First time configuration tour will be implemented.

    During the re-boot, the following will appear on screen:

    Reset The IOCOMM will now reset.
    All connections will be dropped.
    Please wait for 2 minutes and then reconnect to the IOCOMM.


    Note: When the IOCOMM is being re-booted, the Web browser connection is terminated.

  2. Wait two minutes, re-enter your hostname or IP address and you will be presented with the IOCOMM Administration page.

000127


Links to Configuration Tasks

Getting Started | Web Access | First Time Configuration Tour | Configuring DNS on IOCOMM | Changing Serial Line Configuration | Resetting a Serial Port | Using a Modem for Dial-in Operation | Outgoing Services | Disabling Incoming Calls by Port | Adding a Terminal | Configuring the Synchronous Port (B) | Printing | Configuring RADIUS | Local Authentication | Dynamic Routing (RIP) | Enabling TCP Security | Global Messages | Configuring Status Logging | Telnet Service (telnetd) | Monitoring Status | Making Changes to IOCOMM