Introduction to Classic Maps (Views)

Download this manual as a PDF file

A Classic Map (View) is a graphical representation of a group of devices. The Classic Maps page (Maps > Classic Views, formerly the Views tab in the classic user interface) allows you to view and edit maps and relationships between devices and virtual infrastructure. In SL1, views are organized by device group, organization, device category, component maps, Layer-2 topology, CDP topology, LLDP topology, Layer-3 topology, or Virtual Infrastructure (VMware and virtual machines).

In the classic user interface only, you can also create your own classic maps with your most important devices, and add images, text, links, and shapes to customize your maps.

Use the following menu options to navigate the SL1 user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Overview of Device Relationships

SL1 automatically defines parent and child relationships for certain devices. Users can also manually define some types of relationships. Devices can have the following types of relationships:

  • Layer-2 devices and their clients. Layer-2 relationships are automatically discovered by SL1 and can be created in the Subnet Map (L2) page (Maps > Classic Maps > Topology Maps > Layer-2).

  • Layer-3 devices and layer-2 devices. Layer-3 relationships are automatically discovered by SL1 and can be created in the Layer 3 Map page (Maps > Classic Maps > Topology Maps > Layer-3).
  • Network devices that use CDP (Cisco Discovery Protocol) and devices that are specified as neighbors in the CDP tables. CDP relationships are automatically discovered by SL1 and can be created in the Subnet Map (CDP) page (Maps > Classic Maps > Topology Maps > CDP).
  • Network devices that use LLDP (Link Layer Discovery Protocol) and devices that are specified as neighbors in the LLDP tables. LLDP relationships are automatically discovered by SL1 and can be created in the Classic Maps > Topology Maps > LLDP page (Maps > Classic Maps > Topology Maps > LLDP).
  • Component devices and their parent devices using Dynamic Application data. For example, virtual machines and their hypervisors.
  • Device relationships between root devices, parent devices, and component devices (Component Mapping).
  • Device relationships created using Dynamic Application data. For example, the Dynamic Applications in the VMware vSphere and NetApp PowerPacks are configured to create relationships between VMware Datastore component devices and their associated NetApp Volume component devices.
  • Generic parent-child relationships, sometimes referred to as Event Correlation relationships or Ad-Hoc relationships, can be manually created. These relationships can be created in the Device Children page for the parent device.

NOTE: SL1 also automatically discovers relationships between VMWare hypervisors and VMWare virtual machines using SNMP data, but only for legacy versions VMWare ESX 3.5 and VMWare ESX 4.x.

All device relationships are displayed as child and parent relationships. For example:

  • A layer-2 switch is a parent device and a firewall attached to the switch is a child device.
  • A layer-3 router is a parent device and a layer-2 switch attached to the router is a child device.
  • A VMware ESX server is a parent device and a Linux VM on that server is a child device.

Views that Display Device Relationships

The following options on the Classic Maps page (Maps > Classic Views) display device relationship information. Relationships are displayed in a map only if both the parent device and the child device are displayed in the map: