Status indicators and map options

Devices on a Map are dynamically updated according to their status. Devices that don’t respond on ICMP echo requests get a red cross over their surface. Devices for which a “Thresold violation”, “Trap received” or “Anomaly detected” event is pending get a small notification icon. Maps are automatically updated when something changes.

map-example1-1

The image above shows a screenshot of a map. From the various indicators we learn that:

  1. There’s a pending Threshold violation alert for device Calcium. Calcium is also the windows server on which Quantellium is running.
  2. Device Platinum has sent an important Syslog message.
  3. Device Switch has sent a Trap and a Syslog message.
  4. The wireless access point Bromine is down.
  5. The connections Gold-Switch & Platinum-Switch are 16% utilized.
  6. There’s another map in the project called DMZ.

The gray or green lines between the objects are “connections” in Quantellium terminology. The green (16%) labels are the result of Connection Utilization Coding functionality.

Networks, layers and Maps

Larger network infrastructures are usually built up of connected WAN, LAN and MAN networks. Each network can be further divided into layers (IP subnet or VLAN). Quantellium supports such a layered structure. A well defined layered map hierarchy contributes to a clearer view of the infrastructure, a better understanding of status- availability- and health monitoring and helps to understand the consequences of a critical failure more quickly.

The Maps are accessible for all users, regardless of their authorization level. Only users with Administrator rights can create, modify or delete maps or add, modify or delete objects to/from maps!

The default Map

Each Quantellium project has at least one map, the default, system generated map (map-ID=0). This map contains all devices that have not yet been assigned to a custom map. The default map can not be deleted!

The Maps list

Since Map names and Descriptions are frequently used on various pages of a project, it is important to choose them carefully! To add/modify or delete a map, open the “Maps list”. A screen shot of an example list is shown below.

The-Maps-list

An example maps list.

Map Properties:

  • Map name: The Map name is a required field. Only characters from the limited set are allowed. There is no restriction on the string length but for sorting purposes the name should begin with a letter (a..z,A.. Z).
  • Map description: A string that describes the map. Is it a building, a floorplan, a city or a patch-cabinet? There’s no limitation on the length of the description but only characters from the limited set are allowed.
  • Rootmap: In a hierarchical multilayered map structure, only one map can be the RootMap. The RootMap is the highest level Map. Browsing through the maps is like zooming in to a lower level map. The Rootmap is used in the “First page” pane on the Various system settings page!