![background image](http://html1.mh-extra.com/html/patton-electronics/foresight-6100-element-management-system/foresight-6100-element-management-system_user-manual_4035480012.webp)
1 • ForeSight 6100 EMS overview
ForeSight 6100 EMS User Guide
10
Introduction
choosing the web page option from a pop-up menu, in which case a web browser launches and displays the
node’s web page from which it can be managed, or by choosing the Telnet option, which launches the Telnet
client application.
Note
Because of the wide variety of devices that can be managed by the
ForeSight 6100 EMS, this guide does not describe how to configure a
node from its web pages or by using a Telnet client. Instead, refer to
the documentation that came with each device to learn how to con-
figure it via the web or a Telnet interface (or through the device’s con-
sole interface, if it is so equipped).
Container types
The ForeSight 6100 uses containers to organize network elements in a way that is easily understood. Contain-
ers can hold multiple containers and nodes, as shown in
figure 2
on page 9 where the
Bldg-B
container holds
the
1001MC
node
and
the
ForeFront
chassis container (which in turn contains several 3096RC nodes). The
ForeSight 6100 uses the following types of containers (see
figure 2
on page 9):
•
Root container
•
Standard container (referred to simply as
container
)
•
Chassis container (ForeFront AIS)
The Root container (see
figure 2
), the topmost container in the heirarchical tree, always appears when the Fore-
Sight 6100 application is running. There can only be one Root container and it cannot be deleted.
Any container that hold containers is a parent container (the container inside the parent is a child container).
Depending on how it is being considered in the heirarchical tree structure at the time, the same container can
be a parent or a child. For example, as shown in
figure 2
on page 9, the container
Bldg-
B is a child of the
Root
container, but
Bldg-B
is also a parent to the
ForeFront
container. The Root container is a parent, and it alone
can never be a child because it cannot be placed inside another container.
Containers can be organized as desired, but the most common method is to group them by physical location as
shown in
figure 2
on page 9. For example, if you were organizing containers based on the university network
shown in
figure 1
on page 8, you could group them by location as follows:
•
Building A (Administration), which contains a Model 3095, would be created under
Root
as container
Bldg-
A
containing the Model 3095 node named
Admin
.
•
Building B (Physics/Engineering), which contains a 1001 rack in the Physics department and a ForeFront
AIS in the Engineering department, would be created under
Root
as container Bldg-B. The 1001 rack node
would be a labeled Physics. The 3096RC blades installed in the ForeFront AIS would be shown inside a
chassis container and would be labeled Engineering-1 through Engineering-8.
Note
The chassis container is a type of container that is only used with Fore-
Front managed nodes (see section
“The Chassis”
on page 56).