Using Topology Views
EPICenter Concepts and Solutions Guide
59
The second event occurs at point X, because the sample value has fallen below the falling threshold,
which is defined as 80% of the rising threshold value. The third event occurs at point A because the
sample value is again above the Rising Threshold after having fallen below the Falling threshold. At
point B the value again passes the Rising Threshold, but no alarm is generated because the value has
not yet become less than the Falling threshold. Another Rising threshold alarm cannot occur until after
a Falling threshold event has occurred, which happens at point Y. The next Rising threshold event
happens at point C.
Note that in order to have any of these events cause an alarm in the EPICenter Alarm System, you need
to define an alarm that responds to a CPU Utilization Rising Threshold or CPU Utilization Falling
Threshold event.
● If you define an alarm based on the CPU Utilization Rising Threshold event, an EPICenter alarm will
occur at the initial sample, and at points A and C. Because the alarm was defined to respond to CPU
Utilization Rising Threshold events, the falling threshold trap events that occur at points X and Y do
not trigger an EPICenter alarm.
● If you also define an alarm based on a CPU Utilization Falling Threshold event, then EPICenter
alarms would be generated at points X and Y.
Using Topology Views
EPICenter topology views let you create visual representations of your network showing the devices,
links between devices, and basic status of those devices and links, including link utilization statistics
and VLAN membership and configuration information.
EPICenter automatically creates a default view with a set of network maps based on the IP addresses of
the management interfaces in the devices on your network. You can create multiple additional Topology
views to meet whatever needs you have. You can create Topology views that represent the physical
topology of your network (buildings, floors, wiring closets and so on), the logical topology of your
network (by operating divisions, departments, or workgroups) or by functional groupings (core devices
vs. edge devices, ESRP devices, EAPS rings, and so on).
A Topology View consists of a root map and submaps. Within a given Topology view, devices can be
represented only once, but the same devices can appear in multiple Topology Views—while the maps
and submaps within a view are interrelated, Topology Views are independent of each other. This allows
you to create multiple views of your network for different purposes.
To Next Page
Loading...
Need help?
General
