Customized Maps

This section covers the use of customized maps, which you can create to view the devices and links that are most important to you.

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 ().

About Customized Maps

A customized map allows you to view the devices and links that are most important to you.

When you create a customized map, you are also creating a new device group (which appears in the Device Groups page). You can add devices and other sub-device groups to the new map, just as you would to a standard device group.

If SL1 has information about the relationships between the devices in a customized map, SL1 automatically includes the appropriate links in the customized map. Customized maps display every type of relationship data, which includes:

Layer-2 devices and their clients
Layer-3 devices and layer-2 devices
Component devices and their parents, e.g. virtual machines and their hypervisors
Network devices that use CDP (Cisco Discovery Protocol) and devices that are specified as neighbors in the CDP tables
Network devices that use LLDP (Link Layer Discovery Protocol) and devices that are specified as neighbors in the LLDP tables
Device relationships created with Dynamic Applications
Manually created parent-child relationships that affect event correlation

Customized maps appear in the following sections:

My Customized Maps. Personalized maps that you create.

User Customized Maps. If you are a user of type "administrator", you can navigate to the maps in this section to view and edit all customized maps in SL1, even if the device group associated with the map was defined with the field Shared (visible to all users) set to no.

Shared Customized Maps. If a customized map or device group is defined as "shared", you can view the maps in this section. The maps in Shared Customized Maps require the same Access Hooks and Access Keys as device groups. Depending upon the Access Keys assigned to your account, you might be able to edit Shared Customized Maps created by other users. For more information, see the section on Access Permissions.

NOTE: If you create a device group from the Device Groups page and set the Visibility field to include Maps/Views, the device group will appear as a map in the Custom Device Group Map page (Maps > Classic Maps > My Customized Maps). If you set the Shared field to yes, the device group will appear for view by other users as a map in the Shared Customized Maps page (Maps > Classic Maps > Shared Customized Maps).

When you edit a view-only relationship, the change is made only in that map. When you edit a CDP, LLDP, Layer-2, Layer-3, or Event Correlation relationship, the changes are applied throughout SL1.

Creating and Populating the Device Group

When you initially create a customized map and add devices and device groups to the customized map, you are actually defining a device group; however, you are using the maps interface instead of the Device Groups page to do so.

NOTE: You can also create a device group from the Device Groups page. If you select Maps in the Visibility field, the device group will appear as a map in the Custom Device Group Map page (Maps > Classic Maps > My Customized Maps). If you set the Shared field to yes, the device group will appear as a map in the Shared Customized Maps page (Maps > Classic Maps > Shared Customized Maps).

NOTE: By default, device groups created in the Custom Device Group Map page include only Maps/Views under Visibility and have Shared set to no. However, you can change these default settings by editing the device group from the Device Groups page.

To create a new customized map:

Go to the Custom Device Group Map page (Maps > Classic Maps > My Customized Maps > New Group/Map).
In the map pane, select the Edit:Nodes button to add devices and optionally device groups to your customized map.
To add a device to the Customized Map, in the Nodes menu at the top of the pane, select the Add Dev icon. When the Device Browser modal appears, search for the device(s) you want to add to the customized map. Select the checkbox for one or more devices you want to add to the customized map.
To add a device group to the Customized Map, in the Nodes menu at the top of the pane, select the Add Group icon. When the Device Browser modal page appears, search for the device group(s) you want to add to the customized map. Select the checkbox for one or more device groups you want to include in the customized map.
To delete a device from the Customized Map, select the device's icon, select the Edit:[Nodes] button to make the Nodes menu appear at the top of the pane, and then select the Delete icon ().
To delete a device group from the Customized Map, select the device group's icon, select the Edit:[Nodes] button to make the Nodes menu appear at the top of the pane, and then select the Delete icon ().

NOTE: If a device group includes a dynamic rule, SL1 will examine the rule and automatically add devices that match the rule's criteria to the device group. If you delete a device that SL1 has automatically added to the device group, the device will reappear the next time you view the device group map. For details on device groups and dynamic rules, see the Device Groups and Device Templates section.

If SL1 detects Layer-2, Layer-3, CDP, LLDP, VMware, or Component Mapping relationships between the devices, SL1 automatically includes the appropriate links in the customized map.
After you add devices and device groups to the map, you can manually create links and edit existing links.
Clicking on an icon for a device group displays the customized map for that device group.
When you select the Edit:Save button, SL1 prompts you to provide a name for the new customized map.

Creating, Editing, and Deleting Links

In a customized map, you can create links between two devices, edit links between two devices, and delete links between two devices. You can also confirm a relationship between two devices.

In a customized map, you can create the following types of links:

Visual Relationship (this map only). Visual Relationships appear only in the My Customized Maps section. In My Customized Maps, if SL1 has not already discovered another type of relationship between two devices, each manually created link initially has this type of relationship. For Visual Relationships, you can optionally convert the relationship to other types of relationships.
CDP Relationship. CDP relationships appear only in the My Customized Maps section and CDP maps pages. Cisco Discovery Protocol (CDP) allows discovery of Cisco hardware and allows Cisco hardware within the same LAN or WAN to share information about each other. This information includes the MAC address and IP address, the operating system, and information about the network interface. CDP uses a layer-2 protocol that uses the Data Link Layer and is unrouted. CDP can also run on legacy Hewlett Packard Hardware.
LLDPRelationship. LLDP relationships appear only in the My Customized Maps section and LLDP maps pages. Link Layer Discovery Protocol (LLDP) allows discovery of hardware and allows hardware within the same LAN or WAN to share information about each other. This information includes the MAC address and IP address, the operating system, and information about the network interface. LLDP uses a layer-2 protocol that uses the Data Link Layer and is unrouted.

Event Correlation Override. Event Correlation relationships appear only in the My Customized Maps section. If you want to manually define a parent device and child device for two devices that do not share a Layer-2 link, Layer-3 link, a CDP link or a VMware relationship, you can create an Event Correlation Override link between the devices.

Layer 2 Relationship. layer-2 relationships appear only in the My Customized Maps section and Layer-2 Maps pages. Layer-2 links use the Data Link Layer and allow devices in a WAN or LAN to communicate with one another. Layer-2 links use Ethernet and MAC addresses to communicate with devices in the same LAN or WAN. layer-2 links are unrouted.

Layer 3 Relationship. Layer -3 Relationships appear only in the My Customized Maps section and Layer 3 Map page. Layer-3 links use the Network Layer and allow devices from different subnets or networks to communicate. layer-3 links use IP addresses and therefore are routed and can pass messages through routers.

SL1 uses CDP, LLDP, Event Correlation, Layer-2, and Layer-3 relationships for event correlation. For details on event correlation, see the section on Event Correlation and Precedence. When you add devices to a customized map, SL1 automatically adds all links that it has discovered.

If SL1 does not discover a link, you can manually create the link in a customized map. For CDP, LLDP, Layer-2, and Layer-3 links, the newly created links will also appear in the appropriate maps. The manually created link will be saved in SL1. SL1 will not overwrite the new link. Manually created links have precedence over automatically discovered links in Layer-2, CDP, and Layer-3 maps.
If SL1 discovers a link but the link information is incorrect, you can manually edit the link in a Customized Map. For CDP, LLDP, Layer-2, and Layer-3 links, the edited information will also appear in the appropriate maps. The edited link will be saved in SL1. SL1 will not overwrite your changes to the link. Edited links have precedence over automatically discovered links in Layer-2, CDP, LLDP, and Layer-3 maps.

Creating a Link in a Customized Map

If SL1 does not discover a link, you can manually create the link in a Customized Map. You can also create Visual Relationship links and Event Correlation links.

To create a link in a Customized Map:

Go to Maps > Classic Maps > My Customized Maps. Select the Customized Map you want to edit.
When the Customized Map appears in the pane, select the Edit: Links button.
Find the device icon for the parent device. Click on it.
Find the device icon for the child device. Click on it.
SL1 creates a link between the two icons.

When the Link Editor modal page appears, you can edit the values in each field. By default, links created in a Customized Map are a visual relationship, which are shown only on the view for the current map and are not used in event correlation. You have the following options in the Node Relationships pane:

Visual Relationship (this map only). Visual Relationships appear only in the Customized Maps page. In My Customized Maps, if SL1 has not already discovered another type of relationship between two devices, each manually created link initially has this type of relationship. For Visual Relationships, you can define the following:

Device. Displays the name of the device at one end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.

Device. Displays the name of the device at the other end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
Convert Relationship to. For relationships that are initially defined as Visual Relationships, SL1 allows you to convert these relationships to Event Correlation, CDP, Layer 2 or Layer 3.

Event Correlation Override. Event Correlation relationships appear only in the Customized Maps page. If you want to manually define a parent device and child device for two devices that do not share a layer-2 link, layer-3 link, a CDP link, an LLDP link, or a VMware relationship, you can create an Event Correlation Override link between the devices. Additionally, you can then define an event hierarchy for these devices. For Event Correlation Override relationships, you can define the following:

Device. Displays the name of the device at one end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
Device. Displays the name of the device at the other end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.

CDP Relationship. CDP relationships appear only in Customized Maps pages and CDP maps pages. Cisco Discovery Protocol (CDP) allows discovery of Cisco hardware and allows Cisco hardware within the same LAN or WAN to share information about each other. This information includes the MAC address and IP address, the operating system, and information about the network interface. CDP uses is a layer-2 protocol that uses the Data Link Layer and is unrouted. CDP can also run on legacy Hewlett Packard Hardware. For CDP relationships, you can define the following:

Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
VLAN. Displays the VLAN created by the link.

LLDP Relationship

Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.

Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.

VLAN. Displays the VLAN created by the link.

Layer 2 Relationship. Layer-2 relationships appear only in Customized Maps pages and layer-2 maps pages. Layer-2 links use the Data Link Layer and allow devices in a WAN or LAN to communicate with one another. Layer-2 links use Ethernet and MAC addresses to communicate with devices in the same LAN or WAN. Layer-2 links are unrouted. For layer-2 relationships, you can define the following:

Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
Interface. Displays the name of the interface at one end of the link. You can select a different interface on the device. You can then specify this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
VLAN. Displays the VLAN created by the link.

Layer 3 Relationship. Layer 3 Relationships appears only in the My Customized Maps pages and layer-3 Maps pages. Layer-3 links use the Network Layer and allow devices from different subnets or networks to communicate. Layer-3 links use IP addresses and therefore are routed and can pass messages through routers. For Layer 3 Relationships, you can define the following:

Device. Displays the name of the device at one end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.
Device. Displays the name of the device at the other end of the link. You can specify whether this device is a parent, sibling, or child (as compared to the other end of the link). Editing the parent/sibling/child setting in this field also changes the setting in the Device field.

Editing a Link in a Customized Map

If SL1 discovers inaccurate information about a link, you can manually edit the link's properties. You can also edit a link that was manually created.

To edit a link in a Customized Map:

Go to Maps > Classic Maps > My Customized Maps. Select the Customized Map you want to edit.
When the Customized Map appears in the pane, select the Edit: Links button.
Select the link you want to edit.
Select the Edit Link icon in the Link menu (at the top of the pane).
When the Link Editor modal page appears, you can edit the values in each field.
To save your changes, select the Edit: Save button.
The manually edited link will be saved in SL1. SL1 will not overwrite the edited link.

Deleting a Link in a Customized Map

If SL1 discovers a link that you do not want to appear in a Customized Map, you can delete the link. You can also delete links that were created manually.

NOTE: When you delete a layer-2 link, layer-3 link, CDP link, or LLDP link from a Customized Map, the link is not removed from the Layer-2 Map, Layer-3 map, CDP Map, or LLDP Map. The link is removed only from the display of the Customized Map.

To delete a link from a Customized Map:

Go to Maps > Classic Maps > My Customized Maps. Select the Customized Map you want to edit.
When the Customized Map appears in the pane, select the Edit: Links button.
Select the link you want to delete.
Select the Del Link icon in the Link menu (at the top of the pane).
To save your changes, select the Edit: Save button.
The deleted link will no longer appear in this Customized Map.

Viewing and Filtering Customized Maps

To view a Customized Map, go to the Views tab. Go to the left NavBar. Expand the links for My Customized Maps, User Customized Maps, or Shared Customized Maps. Select a device group to view. The Customized Map page appears and displays a map of the device group. Customized maps display:

The blank field in the upper right allows you to find one or more devices in the map. You can enter a string, and SL1 will highlight only the devices that have a device name that matches the string. Each device appears as an icon in the map.
Each network device is connected to its parent device with a line. The color of the line specifies the current state of the connection at each end. The state reflects the event of the highest severity for the network connection. For example, a link line that is red on the child end and yellow on the parent end can indicate that the child device has a critical event and the parent device has a minor event.

NOTE: If all or part of a link are white, this means that SL1 could not determine the interface state or device state for that end of the link.

Each device icon has a color outline. The color of the outline specifies the current state of the device. The state reflects the event of the highest severity for the device.
When the map appears, you can view and reposition the components.The map can be edited and re-arranged using drag-and-drop features. Devices and links can be repositioned for easier reading, if necessary.
Mousing over a device displays its name, IP address, device type, and device category.
Mousing over a link displays as much of the following information as SL1 can retrieve about both the parent and child interface: the MAC address, vendor, interface name, interface alias, and IP address.
If the nodes in the map are using Extended display (Edit: Nodes), you can click on an icon to view events on the device (), create a ticket about the device (), view the Device Summary page (), print a report about the device (), or view the Device Properties page ().

Filtering the Nodes in a Customized Map

You can use the Filter tool to filter the nodes that are included in the current map.

Selecting the Filter icon () toggles on and off the display of the Node Filters checkboxes.

These checkboxes allow you to filter the nodes included in a map based on whether a device or connection is managed or unmanaged in SL1, whether the node is part of a device group, the status of the device (healthy, notice, minor, major, critical), or the device category assigned to the device.

To use the Filter tool:

Go to Custom Device Group Map or Maps > Classic Maps > User Customized Maps or Maps > Classic Maps > Shared Customized Maps. Select the map you want to view.
After the map is displayed, select the Filter tool () in the upper left.
SL1 displays a pane with the Node Filters checkboxes.

Select a checkbox to include the devices in the map.
Unselect a checkbox to remove the devices from the map.

You can select or unselect one or more of the following filters:

Managed Devices. If selected, the map will include devices that are managed by SL1. Managed devices are those that have been discovered with discovery.
Unknown Connections. If selected, the map will include connections that are "unknown" to SL1. This means that SL1 has detected a connection but cannot provide details on all or one end of the connection.
Device Groups. If selected, the map will include device groups.
Unmanaged Devices. If selected, the map will include devices that are not managed by SL1. This means that SL1 has detected a device but has not performed discovery on that device.
Unconnected Nodes. If selected, the map will include devices that are not connected to core devices. The device group defines the core devices. Those devices that are statically assigned to the device group are core devices. For dynamic rules in a device group, the seed devices (those devices that match the specified criteria for the group) are core devices.
Healthy. If selected, the map will include devices with a status of "healthy". This means that the most severe event associated with the device has a severity of "healthy".
Notice. If selected, the map will include devices with a status of "notice". This means that the most severe event associated with the device has a severity of "notice".
Minor. If selected, the map will include devices with a status of "minor". This means that the most severe event associated with the device has a severity of "minor".
Major. If selected, the map will include devices with a status of "major". This means that the most severe event associated with the device has a severity of "major".
Critical. If selected, the map will include devices with a status of "critical". This means that the most severe event associated with the device has a severity of "critical".
Unknown. If selected, the map will include devices with a status of "unknown". This means that SL1 cannot determine the most severe event associated with the device.
List of Device Categories. The pane includes a checkbox for each device category associated with the current map. For each selected device category, the map will include devices with that device category.
Component Mapping. If selected, the map will include devices with links that represent relationships created by dynamic applications.
List of Virtual Relationships. List of all virtual relationships in the map. If selected, the map will include devices with links that represent relationships created by applications like VMware or Azure.