Allied Telesyn International Corp TurboStack AT-S6 User's Guide download pdf (Page 13)

AT-S10 Management Software User’s Guide

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 ﬂoors, 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 efﬁciency 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 ﬂoor, for example, you may decide to manage each hub locally in a

standalone conﬁguration.

If you have many geographically dispersed subnetworks, each connected

to its own department concentrator, management of these multiple hubs

remotely in a central-site conﬁguration requires TCP/IP network

management and a commercially available network management

platform such as HP OpenView™.

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 Conﬁguration 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.

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 77 78

No comments

Allied Telesyn International Corp TurboStack AT-S6 User's Guide Page 13