Copyright 1997 Allied Telesyn International Corp.
All rights reserved. No part of this publication may be reproduced without prior written permission from Allied
Telesyn International Corp.
Allied Telesyn reserves the right to make changes in specifications and other information contained in this document
without prior written notice. The information provided herein is subject to change without notice. In no event shall
Allied Telesyn be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not
limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied
Telesyn has been advised of, known, or should have known, the possibility of such damages.
AT-View and CentreCOM are registered trademarks of Allied Telesyn International Corp.
Turbo Stack, Omega Local, and Omega Remote are trademarks of Allied Telesyn International Corp.
UNIX is a registered trademark of X/Open Company Limited. Windows is a trademark of Microsoft Corporation.
All company names, logos, and product designations that are trademarks or registered trademarks are the property of
This guide describes the procedures to manage the Turbo Stack™ series of
management hubs using the software, AT-S10, and its management
agent, Omega.
The software is pre-installed in Turbo Stack management hubs.
Audience
This guide is written for you, the technical person responsible for
managing Turbo Stack hubs. You must be familiar with Ethernet networks
and the devices used in these networks.
Before using this guide, you must have at least one management
Turbo Stack hub installed and operational in the network.
How this Guide is Organized
This guide consists of the following chapters and appendices:
Chapter 1, “Overview,” describes the features of the pre-installed AT-S10
software and Omega, the management agent.
Chapter 2, “Getting Started,” describes the initial setup steps for you to
begin managing your Turbo Stack hub, and also introduces you to Omega’ s
user interface.
Chapter 3, “Management Menus,” describes the menus you use to
configure and manage Turbo Stack hubs.
Chapter 4, “Fault Tolerance,” describes the process by which modules in
the chassis automatically adapt to module failures and preserve
configuration data.
vii
Preface
Document Conventions
❑
❑
❑
❑
❑
Chapter 5, “Software Upgrades,” describes the procedures to install the
latest software in Turbo Stack hubs.
Appendix A, “Technical Support Fax Order,” is a form on whic h you record
problems with the product to send to Allied Telesyn Technical Support.
Appendix B, “AT-S10 Management Software User’s Guide Feedback,” is a
form on which you record your comments on this guide to send to Allied
Telesyn Technical Communication.
Appendix C, “Where To Find Us,” provides information on Allied Telesyn’s
worldwide locations.
Refer to Allied Telesyn’s web site for a glossary of networking terms. See
Appendix C for the location.
The following conventions are used in presenting information in this
guide:
This guide refers to two or more chassis-mounted hubs as a
department concentrator. The term hub refers to either a standalone
hub or a department concentrator configuration. Each installed
hub in a chassis is called a module .
Menus, commands, prompts, file and pathnames, and other
system-related information displayed by the user interface appear
in Courier typeface; for example:
Select Administration from the main menu.
Text in
boldface
Enter
are entries you must type; for example:
N
to get the Network Parameters menu.
When directed to enter something, you must type the required
characters and then press the
you to press the
Return
key after making an entry unless the action
Return
key. This guide will not direct
will cause a change to take effect. For example:
1. Enter
2. Press
0
for no parity.
Return
twice to enable automatic baud detection.
This means you press the
Return
key a total of three times:
after entering the parity value in Step 1 and to let the hub
software check for the terminal’s baud rate in Step 2.
A procedure icon and heading usually denotes an action or a series
of actions you must perform. For example:
To connect to a remote hub:
Numbered steps may follow.
viii
O
❑
❑
AT-S10 Management Software User’s Guide
❑
Note icon:
NOTE
Notes indicate additional information.
Caution icon:
CAUTION
Cautions tell you that a specific action or an omission of a step
will result in equipment damage or loss of data.
Attention icon:
ATTENTION
Attentions tell you about specific actions that are important
and their omission might lead to minor errors.
Related Documentation
The following Allied Telesyn publications provide information to
supplement this guide:
TurboStack Ethernet Hubs with Management Installation Manual
TurboStack Ethernet Slave/Manageable Hubs Installation Manual
TurboStac k 4-, 7-, and 8-Slot Chassis and Backplanes Installation Manual
TurboStac k AT-TSAx Appliqués Installation Manual
ix
Chapter 1
Overview
This chapter describes:
❑
❑
❑
❑
❑
❑
Software Features
Figure 1: AT-TS12TR
Turbo
Stack Hub
The features of AT-S10 and the management agent Omega
An overview of Turbo Stack hub configurations in relation to hub
management
Information on managing a Turbo Stack hub on your network
The interoperability of the AT-S10 software with AT-S4
Figure 1 shows the 12-port AT-TS12TR TurboStack hub.
Each manageable hub is factory-configured with the AT-S10 software and
has the following software features:
IEEE 802.3 compliance; Ethernet Version 1.0 and 2.0 compatible
repeater functionality
Two types of network management capability:
— SNMP
— Omega via ASYNC ASCII terminal port (Omega Local™) or
Telnet (Omega Remote™)
1
Overview
❑
Software upgrade through firmware cassette or downloading via
the network
Redundant links help to ensure connectivity to a critical network
resource, such as the corporate backbone or a server
Inventory control through storage of multiple addresses on MAC
address table
Comprehensive security features to enable:
— Restricted access to the hub’s management interface
— Restricted access to specific ports
— Manual updates to the MAC address table by the user when
secure mode locks MAC address table (no learning)
The TurboStack Hub Configurations
Each manageable Turbo Stack hub is a single building block for both
standalone (hub) and chassis (department concentrator) configurations.
Allied Telesyn supplies the Turbo Stack chassis that offers two
configurations to enable you to build and reconfigure your networks easily,
efficiently, and at minimum expense:
❑
❑
❑
❑
❑
A standard configuration where a fully populated department
concentrator behaves as a single hub in the network topology.
A segmented configuration that holds up to six Turbo Stack hubs
and either an AT-TS90TR or an AT-TS95TR switch occupying the
bottom slot. Each hub is independently connected to the network
backbone through the switch.
The management hub in the uppermost slot is the master module. It
provides agent services for the entire concentrator. Should the master
module fail, the backup takes over the master functions automatically
(as long as the backup module is also a managed hub). You can hot swap
any module to trace faults or reconfigure the concentrator without
network downtime or interrupting hub management functions.
The Turbo Stack series also includes “slave” modules that are not
manageable as standalone devices (the AT-TS12FS/XX, AT-TS24TS, and
AT-TS24TRS models). The slave models, however, can be managed
through a master module housed in the same department concentrator
chassis. In such a department concentrator chassis, the configuration,
status, and statistical information of slave hubs appear on the network
management displays and can be manipulated in the same way as the
data from the manageable modules.
NOTE
This manual refers to two or more chassis-mounted hubs as a department
concentrator. The term hub refers to either a standalone hub or a
department concentrator configuration. Each installed unit in a chassis is
called a module.
2
For information on the hardware installation and connectivity aspects of
manageable TurboStack hubs, see the separate TurboStack Ethernet Hubs With Management Installation Manual shipped with each hub.
Planning to Manage the Hubs
Before installing and connecting TurboStack hubs at various site locations
(such as in closets in a single building, in closets on different floors, or in
different buildings), decide on the number of hubs in your network and
where each hub is to be located. Advanced planning facilitates the
assignment of hub names and IP addresses if you use them. Planning also
maximizes the efficiency of network management once your hubs are fully
installed and operational.
If you have a limited number of workgroup PCs and devices located on the
same floor, for example, you may decide to manage each hub locally in a
standalone configuration.
If you have many geographically dispersed subnetworks, each connected
to its own department concentrator, management of these multiple hubs
remotely in a central-site configuration requires TCP/IP network
management and a commercially available network management
platform such as HP OpenView™.
AT-S10 Management Software User’s Guide
Local management. If you want to manage the hub locally (Omega
Local™), connect a terminal or a PC directly to its RS-232 port and access
the Omega menus (see Chapter 3, “Terminal Configuration Menu,” on
page 41).
Remote management. From a hub you are managing locally, you can
connect to remote TurboStack management hubs and manage them also.
You need one of the following:
❑Its pre-configured MAC address, found on the edge of the right-
hand plastic flap on t he front panel
❑A unique IP address if you have TCP/IP (either you assign one to
the hub or have your BootP server provide the parameters)
❑A unique name that you assign via Omega
Detailed procedures are found in Chapter 2, “Getting Started.”
NOTE
In a chassis configuration where all the manageable hubs share a common
backplane, only the top (or master) module needs to have a TCP/IP address
or hub name. For management purposes only, Omega views the modules in
the chassis as a single hub within the network.
3
Overview
TCP/IP NetworksTo manage the hub in TCP/IP, you first configure its IP parameters or at
least assign a unique IP address to the hub. You have the option to
manage using either SNMP or Omega Remote™ via Telnet.
TCP/IP with BootP. The function of the BootP utility within an IP
server is to enter an IP address into the hub. Whenever you reset the hub
or power it up, it transmits a request packet to the server every three
seconds to obtain IP parameters.
If the requesting hub does not receive a BootP response after the third
request, it continues to operate with a computed pseudo IP address based
on its MAC address.
If the hub receives a BootP response, it extracts the IP address, Subnet
Mask, or Gateway/Router address from the response packet and uses
these parameters to configure itself until the next power-on or reset.
Additionally, if the response packet specifies a filename and a TFTP host
address, then the hub sends a TFTP get request to the specified host
using the specified filename. This initiates a TFTP download of operating
software and allows you to maintain downloaded server software.
NOTE
If only the master module loses power, the concentrator uses the IP address
stored in the backup module. When the master module reinitializes, it does
not send a BootP request packet because it obtains the configuration from
the backup module.
TCP/IP without BootP. To manage the hub with SNMP or via Telnet,
you must manually enter at least the IP address using the Omega menus.
With or without BootP, entering a unique IP address via Omega ensures
this parameter is always available.
Non-TCP/IP
Networks
To manage the hub, connect a terminal to the hub (see Chapter 3,
“Terminal Configuration Menu,” for the procedures). You may then start
Omega and assign a unique name, or use the pre-configured MAC address .
Interoperability with AT-S4
AT-S4 is the management software for Allied Telesyn’s CentreCOM®
hubs, the AT-3600 series . You can mix and match TurboStack and AT-3600
management hubs in a chassis; however, the advanced AT-S10 features
will not be available. You need to insert an AT-S4 cassette version 3.0 or
greater into the TurboStack hub to so it functions as an AT-3600. To
return the TurboStack hub to its original software level, re-insert the
AT-S10 cassette.
Proceed now to Chapter 2 to perform initial management setup.
4
Chapter 2
Getting Started
This chapter describes the following procedures:
❑Connecting a terminal to the hub for local management
❑Initial and optional configurations
❑Starting an Omega session for initial setup
❑Using the Omega menus
❑Connecting to remote TurboStack hubs for remote management
Connecting a Terminal
Before proceeding, make sure you have installed the hub by following the
procedures in the TurboStack Ethernet Hubs with Management Installation Manual and that the hub is functioning as a repeater.
Terminal connection for a local or standalone management involves the
following preliminary set-up steps:
1. Connect the serial port of your terminal or PC to the RS-232 console
port on the front of the hub. For a PC connection, use a straightthrough 9-pin cable.
2. Turn on your terminal or PC and call up the terminal emulator
program.
3. Check your screen display make sure the emulation options are set as
follows:
The Omega program supports automatic baud rate detection, so
you do not have to configure baud rate on the terminal side.
5
Getting Started
NOTE
These configuration options apply whether you are using Windows or a
DOS-based terminal emulator program. To be sure these options are
always available, save them as an Omega file (i.e., OMEGA.TRM). If you
have previously accessed Allied Telesyn devices with existing terminal
settings, use the same ones without recreating a new .TRM file.
4. To activate the emulation program, press Return twice.
This ensures configuration of the appropriate baud rate.
ATTENTION
Be sure you are using a full screen at your terminal or PC. Otherwise, you
may not see all the characters and menu items displayed by the Omega
agent.
You are done with terminal connection.
In future sessions using a PC running Windows, you only have to access
Omega through the terminal emulator program. Pressing Return twice
will display the main menu.
Starting a Session
You are now ready to manage the hub as a standalone (or install it as a
master module in a chassis) and perform initial configurations.
Once you have established a connection to the hub from your terminal, the
main menu of the Omega Local management program appears on your
screen:
Allied Telesyn International AT-TS24TR Stackable Hub: 4.0
Please select an option:
Port status
Hub Statistics
Individual port overview
Security/Source Address Table
Administration
Quit
->
Keep the menu displayed if you want to enter initial setups.
The procedures in this section are about configuring the following options:
Naming the hub. This is not required but will prove convenient when
you start managing multiple hubs.
Entering an IP address. This is required if you have TCP/IP. If you are
using a subnet mask and a router, you must enter their addresses also.
6
AT-S10 Management Software User’s Guide
Assigning a Hub
Name
While specifying an IP or MAC address is enough to communicate with
the hub, names are more descriptive and easier to remember. For the
same reason, plan to assign names to ports as well (described later in
Chapter 3).
To name the hub:
1. Enter A for Administration from the main menu to get the
following screen:
Please select an option:
Hub name
Module name
Omega Options
Network parameters
Terminal configuration
Language/langue/idioma/linguaggio/sprache
Send updated software to another hub
Update software in all hubs
Reset hub configuration to manufacturing defaults
Activity monitor
EtherMeter
Diagnostics
Connect to a remote hub
->
2. Enter
H for Hub name.
The following menu appears:
The Hub’s current name is:
Null (not currently configured)
Please enter a new name, or Return to retain the existing name:
->
3. Enter the hub name, for example, Sunnyvale.
From now on, the name appears at the top of the menus.
You are done naming the hub. Through Omega, you can now connect to
this hub by specifying its name.
CAUTION
Make sure each hub name is unique because the software does not validate
duplicate hub names. If you use duplicate names, you might inadvertently
connect, reconfigure, or download software to the wrong hub.
7
Getting Started
Entering an IP
Address
This section applies only if you have TCP/IP.
The hub needs an IP address so you can communicate with it via T elnet or
SNMP. Other parameters such as subnet mask and gateway addresses are
also required if you have them. As discussed in Chapter 1, you may use
BootP (if you have it) in your IP server to configure the hub with its IP
parameters.
The following procedures ensure your hub is permanently configured with
its own IP parameters, whether or not you have a BootP server.
To enter an IP address:
1. Enter N for Network parameters from the Administration menu.
The following menu appears:
2. Enter A for IP address to get the following menu:
The current Hub IP Address is:
Null (not currently configured)
Please enter a new value, or Return to retain the existing name:
Enter a value in the form of a.b.c.d, where a,b,c, and d are each in
the range 0-255. For example: 128.9.3.1
->
3. Enter the hub’s IP address at the prompt.
The Network parameters menu appears, displaying the IP
address you entered.
NOTE
Each standalone hub in your TCP/IP network must have an IP address.
However, in a concentrator configuration, only the master hub (the module
in the uppermost slot) needs it. The network sees the concentrator as a
single unit through the master.
8
AT-S10 Management Software User’s Guide
4. Continue by entering the letter corresponding to the network
parameter you want to configure, as follows:
B: Subnet mask. This is required if you have it.
C: Gateway address. This is required if you need to send packets
from one IP network to another via a router.
D through G: SNMP Manager address. You may enter the IP
addresses of up to four network management servers that will
receive SNMP trap messages. This parameter is optional.
H: Download password. The default password is ATS10, shown
in asterisks. The download process requires this password to send
software from one hub to another, provided they are all TurboStack
management hubs and they have the same download password.
You may keep the default or change it. If you change the download
password for this hub, it cannot accept software downloads from or
download software to other switches that have a different
password.
NOTE
The software automatically searches for this password during the
download process without requiring you to enter it. This password is
different from the optional system password you configure to limit access
to the hub’s management user interface.
I through J: Community strings. The defaults for the get, set,
and trap community strings are provided and you may keep them.
K: Location. You may enter a 20-character text string to indicate
the physical location of the hub, for example, First Floor, Lab, or
any description that is useful to you. This parameter is optional
and is used for SNMP management.
L: Contact. You may enter a 20-character text string to indicate
the name, phone number, or any useful information to help identify
the person responsible for the hub. This parameter is optional and
is used for SNMP management.
You just completed initial setup for local management of one hub. Other
configuration options are available and the procedures are in Chapter 3.
Most users keep the default, or customize selected options as required by
their environment.
NOTE
If there are other standalone TurboStack hubs on the network and you are
configuring their IP parameters for the first time, connect these hubs to the
terminal and repeat the procedure.
To familiarize yourself with the Omega user interface , proceed to the next
section.
9
Getting Started
Working with the Omega Menus
Once you are in session, the hub is locked from other session requests; for
example, if using Omega Local, others cannot use Omega Remote on the
hub. At initial startup, you are not required to enter a password. You may
configure a system password later (described in Chapter 3, “Password” on
page 36).
Selecting Menu
Options
There are two ways to make menu selections:
❑If the options are numbered, type the appropriate number and
press the Return or the Enter key, or
❑If the options are not numbered, type enough characters of the
option to distinguish it from the other options and then press the
Return or the Enter key.
For example, if the options are:
Alpha
Beta
GAmma
GRemlin
Choose an option by entering either A, B, GA or GR. You can also
enter “?” to display a HELP screen. To guide you, the screen
displays the characters you type in uppercase, such as GAmma and
GRemlin.
NOTE
Omega is generally not case-sensitive. The download password, however,
is case-sensitive (described later in Chapter 3).
Choosing an option often leads to another submenu. You can either choose
an option from the new menu or return to the previous menu by pressing
Return, Esc, or CTL+C.
A few menus (e.g., Port Status menu for modules with high port count)
cannot fit on a single screen. In this case the management agent displays
“more...” on the screen. The remaining text will be displayed when you
enter M.
All menus and messages are multilingual—you can choose a preferred
human language from the following:
You can change the active language by using the Language command
under the Administration menu.
10
AT-S10 Management Software User’s Guide
Configuring Hub
Modules in a
Chassis
If you have a chassis configuration, the main menu lists the installed and
active TurboStack modules, enabling you to control any module from a
terminal connected to the master (the module in the uppermost slot). The
main menu looks like the following screen:
Allied Telesyn International AT-TS24TR Stackable Hub: 4.0
Please select an option:
Port status
Hub Statistics
Module statistics
Individual port overview
Security/Source Address Table
Administration
Quit
Or select a module:
>1-
2-
3-
4-
5-
6-
7-Allied Telesyn AT-TS90TR Ethernet Switch
->
The example shows a 7-slot TurboStack chassis configuration with six
hubs and one Ethernet switch in the bottom slot. All seven modules share
a segmented backplane. If all the slots were filled with TurboStack hubs
only, the software can report up to eight hub modules sharing a standard
backplane.
For more details about various chassis configuration, refer to the
TurboStack 4-, 7-, and 8- Slot Chassis and Backplanes Installation
Manual.
You can assign names of up to 20 characters to:
❑Each module
❑Each port on each module
❑The hub as a whole
You can enable or disable security features for each port or each module.
For example , if you want to restrict access to a specific port or module, you
can lock the MAC address table and manually enter only the MAC
addresses allowed to use that port or module.
NOTE
The security option is not available at the hub level. If you want to keep the
entire hub secure, you must enable the security feature on every module in
the chassis.
11
Getting Started
Ending a SessionEnd an Omega session by selecting Quit from the main menu. This
returns the management agent to an idle, listening state and breaks the
communication link. If connected via a modem, the phone circuit will be
“hung up”; if connected via the network, the virtual circuit will be
disconnected.
NOTE
An Omega session automatically quits if there has been no keyboard entry
after five minutes. This ensures availability for the next management
session. You may change the five-minute timeout value through the
Administration/Omega Options menu.
Managing Remote Hubs
After setting up the first hub, you can connect to other TurboStack
management hubs in your network to set them up. Use the Omega menus
to connect to those hubs.
NOTE
In a non-TCP/IP network, you cannot connect to a remote hub across
network routers.
To manage another hub in the LAN:
1. Select Administration menu from the Omega main menu.
2. Select Connect to a remote hub.
3. Enter the remote hub’s MAC address if this is the first time you are
connecting to it.
In future sessions and after you have configured an IP address or
name, you may also connect to the hub by those parameters.
The Omega main menu on the remote hub appears.
4. Proceed with hub management.
To manage a remote hub management across a WAN:
NOTE
This procedure works only in TCP/IP networks. The target hub must have
an IP address.
1. Connect a modem to the remote hub’s serial port.
2. Select Administration from the Omega main menu on your hub.
3. Select Connect to a remote hub and enter the target hub’s IP
address.
The Omega main menu on the remote hub appears.
4. Proceed with hub management.
12
Using AT-View®
AT-S10 Management Software User’s Guide
You can purchase an optional network management package called
AT-View from Allied Telesyn. This Windows®- and UNIX®-based SNMP
software application offers an easy-to-use and inexpensive graphical user
interface (GUI). AT-View is ideal for simple and fast diagnostics,
configuration, and the monitoring of network devices.
AT-View allows you to perform network monitoring and management
tasks such as:
❑Assign names to hubs, modules, and ports
❑Identify enabled/disabled ports
❑Change the enabled/disabled status of ports
❑Configure polarity correction
❑Set reconnect algorithms
❑Enable/disable link test
AT-View can track 20 current network statistics, including total collisions
and errors. It also offers a graphing capability that facilitates tracking of
network performance trends.
13
Loading...
+ 54 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.