Operation Manual

Getting Started — The Basics
18
IP Parameters Menu
You must choose a protocol for your network: Is it to be a TCP/IP or a
nonTCP/IP network?
TCP/IP Network
Management
If you have many geographically dispersed subnetworks, each connected to
its own department concentrator, you may want to manage these multiple
hubs remotely in a central-site configuration. In this case, TCP/IP network
management may be optimum.
TCP/IP internet addresses consist of user assigned numbers which identify
members of the network.
It normally consists of two fields: network number and host number. TCP/IP
addresses are expressed in the form of a.b.c.d., where a,b,c and d are each in
the 0-254 range. That is, it adheres to the following notation 192.136.118.3 for
example.
NonTCP/IP
Network
Management
In a nonTCP/IP environment, all switches and devices can be identified by
either any name convention of your choice (a switch name) or by a Media
Access Control (MAC) address (also known as an Ethernet address) which
has been assigned and integrated into each switch by the manufacturer.
TCP/IP addresses are not required for local switch management.
To Configure a
TCP/IP Address
You can configure an IP Address through the serial port of the switch and
implementing Omega management or through a BootP server. The local
installation of an IP address requires either a DOS terminal or a Terminal
Emulator Program and serial cable.
Local Installation. Attach your device to the RS232 serial port. Enable
Omega using either a DOS terminal or the terminal emulator program in
Windows. Then enter a TCP/IP address for each device, the format for which
was detailed above.
The appropriate TCP/IP configuration path proceeds through Omega’s Main
menu and System administration submenu to the option IP
parameters. Once this destination is reached, enter the IP address.
Note that all switches have to be either configured with, or without, an IP
address. They cannot be mixed! For example, a hub with an IP address will
not respond to a Connect remote system query from a hub which does
not have an IP address configured.
BootP You may also use a BootP server to automatically configure TCP/IP
parameters.
The process is straightforward, at start-up, if an IP address has not been
configured, your hub will transmit a BootP request to your server
approximately every three seconds until a response is received (up to a
maximum of three request attempts).
If a BootP response is not received, your hub will still operate using either a
switch name or a MAC address.