Managing a Single Device with the Device Administration Panel

This section describes how to use the Device Administration panel in Skylar One.

What is the Device Administration Panel?

Use the Device Administration panel to define how Skylar One interacts with a device. You can define the data to retrieve, how often Skylar One polls the device, and the policies and thresholds that generate events for the device.

To access the Device Administration panel for a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Find the device for which you want to access the Device Administration panel and click its wrench icon (). The Device Properties page appears. From this page, you can access all the pages in the Device Administration panel.
The Device Administration tools include the following tabs and pages.

Tab	Description
Properties	On the Device Properties page, you can edit parameters that affect how Skylar One discovers and monitors the device.
Thresholds	Use the Device Thresholds page to define usage thresholds, performance thresholds, and data retention thresholds for a device. When a device exceeds these thresholds, Skylar One generates an event for the device.
Collections	The Dynamic Application Collections page displays all the Dynamic Applications associated with the device. For Dynamic Applications that collect performance data, the page displays report policies for each Dynamic Application. For Dynamic Applications that collect configuration data, the page displays objects monitored by each Dynamic Application. You can specify a credential for use with the Dynamic Application for the selected device only. You can enable or disable one or more report policies for the selected device only. You can enable or disable monitoring of one or more objects for the selected device only.
Monitors	Use the Monitoring Policies page to define monitoring policies for a device. Use the Monitoring Policies page to define policies that monitor system processes, domain-name availability and lookup speed, email round-trip speed, Simple Object Access Protocol (SOAP) and Extensible Markup Language (XML) transaction speeds, Transmission Control Protocol/Internet Protocol (TCP/IP) port availability, web-content availability, and services. All these monitoring policies can generate events. Skylar One uses the data collected by these policies to create performance reports and graphs. Additionally, you can use the Monitoring Policies page to create, edit, and delete webhook receivers. For more information, see Managing Webhook Receivers.
Schedule	On the Maintenance Schedule page you can view, edit, and schedule downtime for the device.
Logs	The Device Logs & Messages page displays all the messages Skylar One has collected from the device and from Skylar One about the device.
Toolbox	The Device Toolbox page provides access to common network tools. The list of tools available depends on the type of device and the configuration of the device. Use this page to access and run diagnostics on a device without leaving the user interface.
Interfaces	The Device Interfaces page displays detailed information about each network interface on the device. From this page, you can view details about each individual interface and define bandwidth monitoring for the interface.
Relationships	The Device Relationships page displays information about parent-child relationships between devices. From this page, you can view details on the relationships between layer-2 and layer-3 devices, hypervisors and their virtual machines, and other relationships.
Tickets	The Ticket History page displays all tickets associated with the device. This page displays critical information about each ticket. If you need more detail, you can access the Ticket Editor from this page.
Redirects	Use this page to redirect log entries from one IP-based device to another IP-based device or to a virtual device.
Notes	The Notes & Attachments page displays a list of all comments and attachments associated with the device properties. When you select the Notepad Editor option on the Device Properties page, the notes appear on this page.
Attributes	The Attributes page displays a list of custom attributes that are already aligned with the device. Additionally, on the Attributes page, you can assign a value to those custom attributes, create and align a new extended custom attribute with the device, or delete a custom attribute from a device.

Actions Menu

The pages in the Device Administration panel each include the Actions menu. Use the Actions menu to perform many device-related tasks without leaving the current page. The Actions menu looks like a button and appears in the upper-right corner of the page.

The following entries in the Actions menu appear only on the Device Properties page:

Add IP Address. Leads to the Add IP Address modal, where you can define an additional IP address for the device. Skylar One continues to use the primary IP Address for communication with the device. For details, see the section on Adding an IP Address to a Device.
Select Primary IP Addresses. Leads to the Select Primary IP Addresses modal, where you can define primary IP addresses and secondary IP addresses for the device. A primary IP address allows Skylar One to align traps and syslog messages with the device. In the case of duplicate primary IP addresses, you can promote a secondary IP address to a primary IP address and demote the duplicated primary IP address.
Clear Device Cache. Clears data about this device from the cache. For details, see the section on Clearing the Device Cache.
Device Class. Leads to the Device Class modal, where you can select a device class to associate with the device. For details, see the section on Device Classes and Device Categories.
Secondary Credentials. Leads to the Secondary Credentials modal, where you can associate additional credentials with the device. Skylar One then uses the primary credential and the additional credentials during discovery for the device. For details, see the section on Aligning a Secondary Credential.

Merge Device. Merges the data from a component device and a non-root physical device into a single device. When you merge a physical device and a component device, the component device no longer appears in the user interface. The physical device appears on the pages that previously displayed the component device. For example, the physical device appears instead of the component device on the Device Components page and the Component Map page. The physical device receives all existing and future data for both devices.

For physical devices, this option leads to the Merge Devices modal, where you can view a list of component devices and select a component device to merge with the current physical device.

For component devices, this option leads to the Merge Devices modal, where you can view a list of physical devices and select a physical device to merge with the current component device.

For details, see the section on Merging Devices.

Unmerge Device. Appears only on the Device Properties page for physical devices. Prompts you to unmerge the component device that has been previously merged with the physical device. For details, see the section on Merging Devices.

You can merge only one component device with a physical device. You cannot merge a component device with a physical device that acts as the root device for a dynamic component map (DCM) tree.

When you merge two devices, the historical device logs for those devices will be merged and are not unmerged when the Unmerge Device option does not unmerge the logs.

In Dashboard widgets, you can search for and filter merged devices by the device class or device category of the physical device or the component device. If you select both device classes or both device categories, a merged device appears twice in a single widget.

When you merge two devices, active events for the component device change to "cleared". The cleared events do not become associated with the physical device. If you unmerge the devices, you cannot move the cleared events back to the component device.

The following entry in the Actions menu appears only on the Device Logs & Messages page:

Export Logs. Exports the log entries to a file on your local computer. You can save the exported file or save and view the exported file.

The following entries in the Actions menu appear on each page in the Device Administration panel:

My Bookmarks. Displays the Administer Bookmarks modal, where you can access predefined bookmarks or save a new bookmark. For more information, see Customizing User Experience.

Create a Ticket. Leads to the Ticket Editor page, where you can define a new ticket about the device. For details, see the section on Creating a Ticket About the Device.
Custom Navigation. Leads to the Custom Navigation modal, where you can define a custom tab for the device administration panel for the current device. The custom tab contains a link to an external URL. For details, see the section on Customizing the Interface for a Device.
Device Children. Leads to the Device Children modal, where you can add child devices to the current device. The current device is the parent device. For details, see the section on Defining Device Relationships.
Device Groups. Leads to the Device Groups modal, where you can assign the device to a device group or remove a device from a device group. For details, see the section on Adding a Device to a Device Group.
Notepad Editor. Leads to the Notepad Editor modal, where you can enter a note to include with the device. The note appears on the Notes & Attachments page for the device. For details, see the section on Adding a Note to a Device.
Product Catalog. Leads to the Product Catalog modal, where you can associate a product SKU with the device or disassociate the device from a product SKU. For details, see the section on Associating a Product SKU with a Device.
Report Creator. Leads to the Report Creator modal, where you can define a device report, including the information to include in the report and the format in which to generate the report. For details, see the section on Generating a Report for a Single Device.
Resource Usage. Leads to the Resource Usage modal, where you can view the list of device logs and device statistics that Skylar One gathers. You can also view where the data resides and how many bytes of data it uses.

Device Properties

On the Device Properties page, you can view basic, read-only information about a device. You can also view and edit the device parameters for discovery (collection).

The settings that you define for the device on the Device Properties page override any system-wide settings.

From the Device Properties page, you can:

View Information about the Device. For more information, see Read-Only Information about the Device.
Edit the Discovery Parameters for the Device. This is described in the section on Editing Device Settings.
Edit the Device Class for the Device. This is described in the section on Device Classes.
Associate an Additional IP Address with the Device. This is described in the section on Adding an IP Address to a Device.
Remove an IP Address from the Device. This is described in the section on Removing an IP Address from a Device.
Manage Primary and Secondary IP Addresses for the Device. This is described in the section on Managing Device IPs.
Clear the Device Cache. This is described in the section on Clearing the Device Cache.
Define Child Devices. This is described in the section on Defining Device Relationships.
Associate a Secondary Credential with the Device. This is described in the section on Aligning a Secondary Credential.
Add the Device to a Device Group. This is described in the section Adding the Device to a Device Group.
Create a Ticket About the Device. This is described in the section Creating a Ticket About the Device.
Define Custom Navigation for the Device. This is described in the section Customizing the User Interface for a Device.
Add a Note to the Device. This is described in the section Adding a Note to a Device.
Associate a Product SKU with the Device. This is described in the section Associating a Product SKU with the Device.
Create or Edit an Asset Record for the Device. This is described in the Asset Management section.
View Resource Usage for the Device. This is described in the section on Viewing Performance Data.
Create a Report About the Device. This is described in the section on Viewing Performance Data.

Viewing Read-Only Information About the Device

Each page in the Device Administration panel and the Device Reports panel displays the following read-only information about the device:

Device Name. Name of the device. When you click this field, the Device Properties page for the device appears.
IP Address /ID. IP address of the device and the device ID of the device. The device ID is a unique numeric identifier, automatically assigned to the device by Skylar One. When you click this field, the Device Properties page for the device appears.
Class. Device class for the device. A device class usually describes the manufacturer of the device.
Organization. Organization associated with the device. When you click this field, the Organizational Summary page for the device's organization appears.
Collection Mode. Collection mode. Choices are "active", meaning Skylar One is periodically collecting data from the device, or "inactive", meaning Skylar One is not currently collecting data from the device. When you click this field, the Remote Port Scanner runs and the Remote Port Scanner modal appears.
Description. For Simple Network Management Protocol (SNMP) devices, the SysDescr value that the SNMP agent on the device reports. If a device does not support SNMP, this field appears blank.
Root Device. For component devices, displays the device name or IP address of the physical device where the system that manages the device resides. When you click this value, the Device Properties page for the root device appears.
Parent Device. For component devices, displays the device name or IP address of the parent device. The parent device can be either another component device or a physical device. A parent device is the device between the current component device and the next layer in the component-device hierarchy. When you click this value, the Device Properties page for the parent device appears.
Device Hostname. For devices that are discovered and managed by hostname (instead of IP address), this field displays the fully qualified hostname for the device.
Managed Type. Specifies the protocol used to discover the device and whether the device is a physical device or a virtual device. Click this field to run an SNMP walk of the device's SNMP file and display the SNMP Walkermodal.
Category. The device category associated with the device. The device category usually describes the function of the hardware.
Sub-Class. The device sub-class associated with the device. The sub-class usually describes the model of a device.
Uptime. The number of days, hours, minutes, and seconds that the device has been continuously up and communicating with Skylar One. When you click this field, the System Vitals Summary report appears.
Collection Time. The date and time that Skylar One last collected data from the device.
Group/Collector. The Collector Group and specific collector used to last collect data from the device. For All-In-One Appliances, this field contains the name of the default, built-in Collector Group.

Editing Device Settings

The fields on the Device Properties page affect how Skylar One discovers and collects information about the device. Initially, Skylar One uses system defaults, system-wide settings, and data retrieved during initial discovery of the device to populate these fields.

You can edit one or more of these fields for the device. The settings that you define for the device on the Device Properties page override any system-wide settings that you define on the pages under System > Settings.

Identification

Device Name. The name of the device. If possible, Skylar One retrieves the device name from the device. If the device is running SNMP or has a DNS entry, the name comes directly from the device. You can set the precedence for which of these names to use (SNMP system name or DNS entry) on the Behavior Settings page (System > Settings > Behavior). You can edit this name on the Device Properties page, but this does not change the name on the actual device.
IP Address. The IP address that Skylar One uses to communicate with the device. You can add additional IP addresses for the device. To change the IP address Skylar One uses to communicate with the device (called the Admin Primary address), select a different IP address in this field.
Organization. Organization to which this device has been assigned. To assign this device to a different Organization, select an Organization from the drop-down list. To view details about the assigned organization, click the organization icon () to the right of this field.

Monitoring & Management

Device Class. Displays the Device Class. To assign a different device class to the device, click the toolbox icon () to the right of this field. To edit the device class for the device, click the pencil icon () to the right of this field.

If you incorrectly change the device class for a device, the Skylar One nightly update overrides the new device class and assigns the device to the correct device class.

SNMP Read /Write. Use the first drop-down field to select an SNMP Read credential for read access to SNMP information on the device. Use the second drop-down field to select an SNMP Write credential for read-and-write access to SNMP information on the device.

Devices that do not support SNMP ("pingable" devices) display the value None in both fields. Also, your organization memberships might affect the list of credentials you can see in these fields.

Availability Port. Specifies the protocol (first drop-down menu) and specific port (second drop-down menu) that Skylar One monitors to determine if the device is available. The list of ports contains all the ports that Skylar One discovers. Device availability reports use the data from this port. Protocol options include:

TCP. Availability is based on whether Skylar One can connect to the device using the specified TCP port.
ICMP. Availability is based on whether the device responds to an Internet Control Message Protocol (ICMP) ping request from Skylar One. If you select ICMP as the protocol, you can use the ICMP Availability Thresholds fields on the Device Thresholds page to further define how Skylar One tests the device availability.
SNMP. Availability is based on whether the device responds to an SNMP get request from Skylar One.
ScienceLogic Agent. Availability is based on whether the Skylar One agent is reporting data to Skylar One. The agent must be installed on the device to use this option.

Component devices use a Dynamic Application collection object to measure availability. For more information, see the description of the Component Identifier field on the Collection Objects page. For more information on availability, see the section Monitoring Device Availability and Device Latency.

Run Availability Policy (). When you click this icon, Skylar One immediately checks the availability of the device, using the port and protocol that you specify in the Availability Port fields. Skylar One displays a Session Logs modal that describes each step of the availability policy in detail. This information helps you troubleshoot availability problems with a device.

Latency Port. Specifies the protocol and specific port that Skylar One monitors to determine latency for the device. The list of ports contains all the ports that Skylar One discovers and the option ICMP, for which Skylar One performs a ping request. Device latency reports use the data from this port or ping request.

If you select ICMP as the protocol, you can use the ICMP Availability Thresholds on the Device Thresholds page to further define how Skylar One tests the device latency.

Avail + Latency Alert. Specifies how Skylar One responds when the device fails an availability check, when the device fails a latency check, and when the device fails both. Use these options to create separate events when SNMP fails on a device and when the device is not available. Choices are:

Enabled. Skylar One creates the following events:

If the device fails the availability check, generates the event "Device Failed Availability Check: UDP - SNMP".

If the device fails the latency check, generates the event "Network Latency Exceeded Threshold: No Response".
If the device fails both the availability check and the latency check, generates the event "Device Failed Availability and Latency checks".

Disabled. Skylar One creates the following events:

If the device fails the availability check, generates the event "Device Failed Availability Check: UDP - SNMP".

If the device fails the latency check, generates the event "Network Latency Exceeded Threshold: No Response".
If the device fails both the availability check and the latency check, generates the event "Device Failed Availability Check: UDP - SNMP". The availability event suppresses the event "Network Latency Exceeded Threshold: No Response".

User Maintenance. Specifies whether the device is in "user maintenance" mode. By default, when a device is in "user maintenance", Skylar One does not generate events about the device.

You can choose to enable or disable polling during "user maintenance" mode. If you enable polling during "user maintenance", Skylar One collects information from the device but generates only events with a severity lower than the severity that you specify in the system-wide Maintenance Minimum Severity setting. For more information on the Maintenance Minimum Severity setting, see the Device Maintenance section.

"User maintenance mode" is not scheduled. You must manually enable "user maintenance" to put a device into this mode. You must manually disable "user maintenance" to turn off this mode for a device. "User maintenance mode" overrides scheduled maintenance for a device. Choices are:

Disabled. The device does not enter "user maintenance" mode.
Enabled. The device enters "user maintenance" mode. When you make this selection, a second field becomes active where you can specify whether Skylar One polls the device during the "user maintenance" mode. During normal operation, Skylar One polls each device as specified by each device's policies and aligned Dynamic Applications. Choices are:

Maintenance Collection Enabled. During "user maintenance" mode, Skylar One continues to poll the device.
Maintenance Collection Disabled. During "user maintenance" mode, Skylar One does not poll the device.

Collection. Specifies whether Skylar One monitors the device. To edit this field, select one of the following from the drop-down list:

Disabled. Excludes the device from monitoring by Skylar One.
Enabled. Includes the device in monitoring by Skylar One. When you make this selection, a second field becomes active where you can specify which collector group performs discovery and gathers data from the device. The drop-down list contains a list of available collector groups. For All-In-One Appliances, this field displays only the built-in Collector Group (and any virtual Collector Groups). For more information on collector groups, see Collector Groups.

Coll. Type. Specifies how Skylar One should perform collection. The choices are:

Standard. Skylar One performs discovery of each device based on the device's IP address. This method is appropriate for devices using standard DNS.
DHCP. Skylar One performs a Domain Name System (DNS) lookup for the device each time Skylar One retrieves information from the device. This allows Skylar One to get the latest IP address for the device.

Critical Ping. Frequency with which Skylar One should ping the device in addition to the five-minute availability poll. If the device does not respond, Skylar One creates an event. The choices are:

Disabled. Skylar One does not ping the device in addition to the five-minute availability poll.
Intervals from every 120 seconds to every 5 seconds.

Skylar One does not use this ping data to create device-availability reports. Skylar One continues to collect device availability data only every five minutes, as specified in the process "Data Collection:Availability" (on the Process Manager page). For more information on critical ping, see the section Monitoring Device Availability and Device Latency.

Because high-frequency data pull occurs every 15 seconds, you might experience up to 15 seconds of latency between an unavailable event and the time that event appears in the Database Server if you set Critical Ping to 5 seconds.

You might experience some performance issues if you have a large number of devices using critical ping on a short polling interval. If you have many devices and events generate late for a critical ping outage, increase the polling interval.

Dashboard. Select a device dashboard from a list of all device dashboards in Skylar One. The selected device dashboard appears by default on the Device Summary page for this device. This field is optional.

Event Mask. Groups events that occur on a single device within the selected time interval. Related events that occur in quick succession on a single device roll up and post together under one event description. Select a time span from the drop-down list:

Disabled. Skylar One does not group events.
Group in blocks at intervals from every 30 seconds to every 1 month

By default, when events are masked, the Events page displays all events that occur on the device within the specified time span under a single event, the one with the highest severity. The magnifying-glass icon () appears to the left of the event. When you click the magnifying-glass icon, the Suppression Group modal appears. The modal displays details about all events that Skylar One masks under the displayed event.

If an event has Occurrence Count and Occurrence Time set on its Event Policy Editor page, Skylar One uses the first logged occurrence of the event to calculate the Event Mask, even if that first occurrence did not appear on the Events page (due to the Occurrence Count and Occurrence Time fields).

For example, suppose an event, event_x, has an Occurrence Count of "3" and an Occurrence Time of "10 minutes". This means that the event must occur on the same device at least three times within 10 minutes before the event appears on the Events page. Suppose the event, event_X, occurs on device_A at 15:51, 15:52, and 15:53. The event appears on the Events page with a timestamp of "15:53", an age of "2 minutes", and a count of "3".

Suppose device_A includes an Event Mask of "Group in blocks every 5 minutes". To calculate how to group event_x, the Event Mask uses the timestamp of the first occurrence, 15:51, even though the event did not appear on the Events page at that time. The Event Mask also uses the time of the first occurrence, 15:51, to calculate the "Age/Elapsed" value for the event in the Suppression Group modal.

Topology Settings

The device initially inherits its topology settings from the system-wide topology settings on the Behavior Settings page (System > Settings > Behavior), or from the topology settings for the device's class. However, you can change these settings on a per-device basis by editing one or more of the fields below. The field labels include either "Inherited" or "Override" to show whether the device inherits the setting or overrides it. For more information on the system-wide topology settings, see the section on Global Settings for System Behavior. For more information on the device class topology settings, see the section on Device Classes and Device Categories.

L2 Topology. Select from the following Layer-2 topology options for the device:
- Disabled. Disables Layer-2 topology collection and processing for the device.
- Processing Enabled. Enables Layer-2 topology processing for the device using the "Enterprise Database: Topology Crunch" process to determine Layer-2 topology relationships based on device category and connects network devices to each other using methods other than the standard SNMP protocol for collection.
- Collection and Processing Enabled. Enables Layer-2 topology collection and processing for the device using the standard SNMP collection methods and the "Enterprise Database: Topology Crunch" process to determine Layer-2 topology relationships based on device category, with the purpose of connecting network devices to each other.
- Enhanced Processing Enabled. Enables advanced Layer-2 topology processing for the device, but using methods other than the standard SNMP for collection. This enhanced processing can form Layer-2 relationships between any devices that match a MAC address from the BRIDGE-MIB or sourced from Dynamic Applications, regardless of device category.
- Collection and Enhanced Processing Enabled. Enables advanced Layer-2 topology processing and collection for the device using the standard SNMP collection methods. This enhanced processing can form Layer-2 relationships between any devices that match a MAC address from the BRIDGE-MIB or sourced from Dynamic Applications, regardless of device category.
- Inherit Class Value. If selected, the device inherits the Layer-2 topology collection and processing settings assigned to its device class.
L3 Topology. Select from the following Layer-3 topology options for the device:
- Disabled. Disables Layer-3 topology collection and processing for the device.
- Processing Enabled. Enables Layer-3 topology processing for the device using the "Enterprise Database: Topology Crunch" process to determine Layer-3 topology relationships. This option requires all hops in a traceroute to respond and match devices within Skylar One to form the relationship.
- Collection and Processing Enabled. Enables Layer-3 topology collection and processing for the device using the "Enterprise Database: Topology Crunch" process to determine Layer-3 topology relationships. This option requires all hops in a traceroute to respond and match devices within Skylar One to form the relationship.
- Enhanced Processing Enabled. Enables advanced Layer-3 topology processing for the device, where the system forms relationships between any two hops that respond and match devices in Skylar One rather than discarding incomplete traceroutes or results that include unmatched hops.
- Collection and Enhanced Processing Enabled. Enables advanced Layer-3 topology processing and collection for the device, where the system forms relationships between any two hops that respond and match devices in Skylar One rather than discarding incomplete traceroutes or results that include unmatched hops.
- Inherit Class Value. If selected, the device inherits the Layer-3 topology collection and processing settings assigned to its device class.
CDP Topology. Select from the following Cisco Discovery Protocol (CDP) topology options for the device:
- Disabled. Disables CDP topology collection and processing for the device.
- Processing Enabled. Enables CDP topology processing for the device using the "Enterprise Database: Topology Crunch" process to determine CDP topology relationships between two devices that both respond with CDP neighbor data, show each other as neighbors, and are managed devices in Skylar One. This option uses methods other than standard SNMP for collection.
- Collection and Processing Enabled. Enables CDP topology collection and processing for the device using standard SNMP collection methods and the "Enterprise Database: Topology Crunch" process to determine CDP topology relationships between two devices that both respond with CDP neighbor data, show each other as neighbors, and are managed devices in Skylar One.
- Enhanced Processing Enabled. Enables advanced CDP topology processing for the device, but using methods other than standard SNMP for collection. This advanced processing can form CDP relationships between two devices if at least one of those devices responds with CDP neighbor data and is a managed device in Skylar One.
- Collection and Enhanced Processing Enabled. Enables advanced CDP topology processing and collection for the device using standard SNMP collection methods. This enhanced processing can form CDP relationships between two devices if at least one of those devices responds with CDP neighbor data and is a managed device in Skylar One.
- Inherit Class Value. If selected, the device inherits the CDP topology collection and processing settings assigned to its device class.
LLDP Topology. Select from the following Link Layer Discovery Protocol (LLDP) topology options for the device:
- Disabled. Disables LLDP topology collection and processing for the device.
- Processing Enabled. Enables LLDP topology processing for the device using the "Enterprise Database: Topology Crunch" process to determine LLDP topology relationships between two devices that both respond with LLDP neighbor data, show each other as neighbors, and are managed devices in Skylar One. This option uses methods other than standard SNMP for collection.
- Collection and Processing Enabled. Enables LLDP topology collection and processing for the device using standard SNMP collection methods and the "Enterprise Database: Topology Crunch" process to determine LLDP topology relationships between two devices that both respond with LLDP neighbor data, show each other as neighbors, and are managed devices in Skylar One.
- Enhanced Processing Enabled. Enables advanced LLDP topology processing for the device, but using methods other than standard SNMP for collection. This enhanced processing can form LLDP relationships between two devices so long as at least one of those devices responds with LLDP neighbor data and is a managed device in Skylar One.
- Collection and Enhanced Processing Enabled. Enables advanced LLDP topology processing and collection for the device, using the standard SNMP collection methods. This enhanced processing can form LLDP relationships between two devices so long as at least one of those devices responds with LLDP neighbor data and is a managed device in Skylar One.
- Inherit Class Value. If selected, the device inherits the LLDP topology collection and processing settings assigned to its device class.

ARP Topology. Select from the following Address Resolution Protocol (ARP) topology options for the device:
- Disabled. Disables ARP topology collection and processing for the device.
- Processing Enabled. Enables ARP topology processing for the device using the "Enterprise Database: Topology Crunch" process to determine ARP topology relationships between two devices that are routers or switches on the same local network, are managed devices in Skylar One, and include a device with an IP address and another with a physical MAC address.
- Collection and Processing Enabled. Enables ARP topology collection and processing for the device using standard SNMP collection methods and the "Enterprise Database: Topology Crunch" process to determine ARP topology relationships between two devices that are routers or switches on the same local network, are managed devices in Skylar One, and include a device with an IP address and another with a physical MAC address.
- Enhanced Processing Enabled. Enables advanced ARP topology processing for the device. This enhanced processing can form ARP relationships between two devices of any device class so long as at least one of those devices responds with ARP data and is a managed device in Skylar One.
- Collection and Enhanced Processing Enabled. Enables advanced ARP topology processing and collection for the device using standard SNMP collection methods. This enhanced processing can form ARP relationships between two devices of any device class so long as at least one of those devices responds with ARP data and is a managed device in Skylar One.
- Inherit Class Value. If selected, the device inherits the ARP topology collection and processing settings assigned to its device class.

Preferences

Auto-Clear Events. Auto Clear automatically removes an event from the Event Monitor if a specified succeeding event occurs. For example, suppose the event "Device not responding to ping" occurs. If the next polling session produces the event "Device now responding normally to ping", the Auto Clear feature can clear the event. If you do not want events to clear automatically, clear this checkbox. For this specific device, this field overrides the global auto-clear settings on the Event Policy Editor page (Events > Event Manager > create or edit).
Accept All Logs. This checkbox specifies whether or not you want to keep and save all logs for this device. If you want to retain only logs associated with events, clear this checkbox.
Daily Port Scans. This checkbox specifies whether or not you want Skylar One to perform a daily scan of the device for open ports. Select this checkbox to enable daily port scans.
Auto-Update. This checkbox specifies whether or not you want Skylar One to perform auto-discovery of the device and update records with changes to the device. Select this checkbox to enable nightly updates. If you clear this checkbox, Skylar One does not perform auto-discovery. Changes to the device, including newly opened ports, are not recorded by Skylar One.
Scan All IPs. If the device uses multiple IP Addresses, Skylar One can scan for open ports on all IPs during auto-discovery. Select this checkbox to scan all IP addresses for open ports every night.
Dynamic Discovery. If selected, Skylar One automatically assigns the appropriate Dynamic Applications to the device during auto-discovery.
Preserve Hostname. If selected, the name of the device in Skylar One remains the same, even if the name of the actual device changes. If you clear this checkbox, the device name updates when the name of the actual device changes.
Disable Asset Update. If selected, Skylar One does not automatically update the asset record associated with the device. For a single device, this checkbox overrides any settings defined on the Asset Automation page (System > Settings > Assets).

Adding an IP Address to a Device

If a device has multiple IP addresses, you can add those IP addresses in Skylar One. Skylar One continues to use the primary IP address for communication with the device. However, after you add an additional IP address to a device, you can change the primary IP address to the new IP address by selecting it in the IP Address field.

To define additional IP addresses for a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device for which you want to define additional IP addresses. Click the wrench icon () for the device.
On the Device Properties page, find the IP Address field.
To the right of the IP Address field, click the plus-sign icon ().
Alternatively, click the Actions menu and select Add IP Address.
The Add IP Address modal appears. Use the Add IP Address modal to define an additional IP address for the device.
Use the Add IP Address modal to define an additional IP address for the device. Skylar One continues to use the Admin Primary IP address for communication with the device. Skylar One also collects data about the additional IP addresses. To associate an additional IP address with the device, enter values in the following fields:

IP Address. Enter the IP address. This can either be a numeric IPv4 address that uses dots or an alphanumeric IPv6 address that uses colons.
Subnet Mask. Enter the subnet mask associated with the IP address. This field is optional.

Click the [Add] button.
On the Device Properties page, the additional IP address appears in the IP Address field. During auto-discovery, Skylar One verifies that this IP address exists on the device and appends the label "verified" to the value in the IP Address field.

After you manually rediscover the device or after Skylar One runs nightly auto-discovery (whichever occurs first), the new IP address appears on the Network Browser page.

Removing an IP Address from a Device

If you have added an IP address to a device using the steps in the section on Associating an Additional IP Address with the Device, you can also delete that IP address.

You cannot delete an IP address in the following cases:

You cannot delete an IP address that is currently the Admin Primary IP address for the device.
You cannot delete an IP address that is associated with a network interface.

To delete an IP address:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device from which you want to delete an IP address. Click the wrench icon () for the device.
On the Device Properties page, find the IP Address field.
To the right of the IP Address field, click the delete icon (). The Remove IP Address modal appears:
Select the checkbox for the IP address you want to delete.
Click the Remove button. Skylar One deletes the IP address.

The Remove IP Address modal displays checkboxes only for IP addresses that you can delete. If an IP address appears in the Remove IP Address modal page without a checkbox, you cannot delete that IP address.

If an IP address that you want to delete appears in the Remove IP Address modal as Selected, it is currently the Admin Primary IP address and you must select a new Admin Primary IP before you can delete the IP address. To select a new Admin Primary IP address:

In the IP address drop-down list on the Device Properties page, select a new Admin Primary IP address.
Click the Save button.
You can now delete the previous Admin Primary IP address.

Managing Device IPs

There are three types of IP addresses that can be associated with a device:

Admin Primary. This is the IP address that Skylar One uses to communicate with a device. This IP address is always a primary address and cannot be demoted to a secondary address. You can change the Admin Primary address by changing the value in the IP Address field on the Device Properties page.
Primary. One or more IP addresses that Skylar One uses to match incoming log messages (traps and syslog messages) with a device. When you select an IP address in the Select Primary IP Addresses modal, that IP address becomes a primary. You can also deselect an IP address on the Select Primary IP Addresses modal. When you deselect an IP address, that IP address becomes a secondary.
Secondary. Skylar One gathers information about this IP address and uses the IP address to match incoming log messages (traps and syslog messages) with a device if it cannot match them first to a primary IP address.

A Message Collection Server accepts inbound, asynchronous messages from monitored devices and applications in your network. For example, Message Collectors accept all SNMP traps, SNMP informants, and syslog messages. A Skylar One system can include one or more Message Collectors.

A single Message Collector can be aligned with multiple collector groups.

If you are using a combination Data Collector and Message Collector, assign this combination appliance only to its own dedicated collector group. Do not add other Data Collectors or Message Collectors to that collector group.

Although Skylar One will not allow duplicate IP addresses within a single collector group, Skylar One does allow duplicate IP addresses if each device is aligned with a different collector group.
If a single Message Collector is aligned with multiple collector groups, the single Message Collector might be aligned with two or more devices (each in a separate collector group) that use the same primary IP address or the same secondary IP address. If this happens, Skylar One generates an event. To correct this situation, go to the Select Primary IP Addresses modal for one of the devices and change the primary IP address in question. Demote the primary IP address and promote a secondary IP address for the device. This resolves the duplicate IP addresses and allows the Message Collector to align messages with the device.

For All-In-One Appliances, the function provided by a Message Collector is built in to the All-In-One Appliance. All-In-One systems contain only one built-in Collector Group.

On the Select Primary IP Addresses modal, you can view a list of IP addresses for the device and define one or more of those IP addresses as "primary" or "secondary". To change an IP address to primary or secondary:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Find the device for which you want to manage the IP addresses. Click its wrench icon ().
On the Device Properties page for the device, click the Actions menu. Select Select Primary IP Addresses.
The Select Primary IP Addresses modal appears. There are three types of IP addresses that can be associated with a device:

Admin Primary. This is the IP address that Skylar One uses to communicate with a device. This IP address is always the admin primary address and cannot be demoted to a secondary address.
Primary. One or more IP addresses that Skylar One uses to match incoming messages (traps and syslog messages) with a device. When you select an IP address in the Select Primary IP Addresses modal, that IP address becomes a primary. You can also deselect an IP address in the Select Primary IP Addresses modal. When you deselect an IP address, that IP address becomes a secondary.
Secondary. Skylar One gathers information about this IP address and uses the IP address to match incoming log messages (traps and syslog messages) with a device if it cannot match them first to a primary IP address.

Within a collector group, multiple devices cannot use the same primary IP address. In some circumstances, an IP address appears in the Select Primary IP Addresses modal for the current device but does not have a corresponding checkbox. This means that the IP address is currently used as a primary IP on another device in the same collector group. Skylar One does not allow you to promote this IP address to a primary IP address on the current device.

Click the Save button to save the changes to the device.

Clearing the Device Cache

Between Hypertext Transfer Protocol (HTTP) requests, Skylar One caches data in memory. For diagnostic purposes, you might want to clear the cached data about a specific device. To clear the cached data about a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device whose data you want to clear from the cache. Click its wrench icon ().
On the Device Properties page for the device, click the Actions menu and select Clear Device Cache. Data about the device clears from the cache.

Aligning a Secondary Credential

During initial discovery of a device, Skylar One uses a specified SNMP credential. If you specified that Skylar One should discover non-SNMP devices, Skylar One uses ICMP and nmap to gather information about a device. After Skylar One finds devices, discovery can use a second list of specified credentials to access database data, SOAP data, XML data, or data that is monitored with a Snippet Dynamic Application.

After initial discovery, you can add additional credentials to a device. For example, if more than one SNMP agent is running on the device, you can now associate each agent with its own credential. If Skylar One monitors multiple applications on the device, you can associate each application with its own credential. During the next discovery session, Skylar One uses the appropriate credential for each agent or application on the device.

When auto-discovery or manual discovery runs on a device, Skylar One uses the credentials in this order: 1) Each credential manually aligned with each Dynamic Application in the Dynamic Application Collections page, in the Device Administration panel; 2) Secondary credentials defined on the Device Properties page, in the Device Administration panel; 3) The SNMP Read/Write string defined on the Device Properties page, in the Device Administration panel; 4) The credential used in the initial discovery session for the device.

To associate one or more additional credentials with a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
In the Device Manager page, find the device for which you want to define additional credentials. Click the wrench icon () for the device.
On the Device Properties page, select the Actions menu and choose Secondary Credentials. The Secondary Credentials modal appears.
The Secondary Credentials modal displays a list of all credentials in Skylar One:

When you define primary and secondary credentials for a device, you see only the credentials that are aligned to organizations that you belong to. If a primary or secondary credential has already been defined on the device, and is aligned to an organization you are not a member of, the credential will be restricted. To learn more about credentials and organizations, see the Discovery and Credentials section.

To add a credential, select an entry in the list of credentials.
To select multiple credentials, press and hold the Ctrl key and click each entry.
To remove all secondary credentials from a device, select the Remove All/None option.

Click the Save button.

Adding the Device to a Device Group

A device group is a group of multiple devices. Use device groups to configure and edit multiple devices at the same time. You can view a list of existing device groups, edit a device group, or define a new device group on the Device Group Editor page (Devices > Device Groups).

Device configuration templates store device configurations. You can apply a template to one or more devices and reuse it. A device template contains predefined settings for all the fields on the Device Properties page (except device name and device IP) and all the fields on the Device Thresholds page. Device templates can also apply policies for interface monitoring, port monitoring, web-content monitoring, service monitoring, and process monitoring and align devices with Dynamic Applications. You can view and define device templates on the Configuration Templates (Devices > Templates, or Registry > Devices > Templates in the classic user interface) page.

You can apply device configuration templates to a device group and automate the initial configuration of multiple devices. You can also use device groups and device configuration templates to modify the configuration of multiple devices.

For more information on device groups and device templates, see the Device Groups and Device Templates section.

To add a device to an existing device group:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device that you want to add to a device group. Click the wrench icon () for the device.
On the Device Properties page, click the Actions menu and select Device Groups. The Device Groups modal appears.
On the Device Groups modal, you can assign a device to a device group or remove a device from a device group.

To add the device to a device group, in the Available Device Groups pane, select one or more device groups. After you click the Save button, the device group appears in the Member Device Groups pane.
To remove the device from a device group, in the Member Device Groups pane, select one or more device groups. After you click the Save button, the device group appears in the Available Device Groups pane.

The Member Device Groups pane displays device groups for which the device is a static member as well as device groups where the device matches a dynamic rule for membership.

Click the Save button.
To remove the device from a device group, in the Member Device Groups pane, select one or more device groups.
Click the Save button.

Creating a Ticket About the Device

A ticket is a request for work. Use tickets to monitor work tasks that relate to your network. You can create a ticket about a device. The ticket can describe a problem with the device or a maintenance task for the device.

For more information on tickets and ticketing, see the Ticketing section.

To create a ticket for a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device about which you want to create a ticket. Click the wrench icon () for the device.
On the Device Properties page, click the Actions menu and select Create a Ticket. The Ticket Editor page appears.
On this page, you can define the basic parameters for a ticket. Notice that the Description field and Element field are automatically populated with the device name.
Click the Save button to save the ticket.

Adding a Note to a Device

You can add notes about a device to the Device Administration panel. The note appears on the Notes & Attachments page (the Notes tab in the Device Administration panel). Each note you add to the device can include formatted text, links, images, videos, and attachments.

To add a note to a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device that you want to add a note to. Click the wrench icon () for the device.
On the Device Properties page, click the Actions menu and select Notepad Editor.
The Notepad Editor modal appears. In this modal, you can enter and format text, include images and links in the message, and include an attachment. Click the Save button to save the note.
Use the Notepad Editor modal to enter notes or comments about the device.

You can format the text and include links, images, and videos in the note.
You can also include a document template (System > Customize > Document Templates) in the field.

The note appears on the Notes tab, on the Notes & Attachments page.
The Notes & Attachments page displays all the notes about the device that you created with the Notepad Editor modal. On the Notes & Attachments page, each entry includes the username, date and time, and text of the comment. You can perform the following on each note entry:

To view a note's attachment, click the paperclip icon ().
To edit the content of a note, click the wrench icon (). The Notepad Editor modal appears. You can update the note; format the text; insert content from a saved template; and add an attachment, image, or video to the note. Click the Save button to save your changes.
To delete a note, click its delete icon ().

For information about adding a note to a device on the Notes tab of the Device Investigator, see the section on The Notes Tab.

Aligning Custom Attributes with a Device

You can align custom attributes with a device, assign values to those custom attributes (for the selected device only), and create new extended custom attributes for a device on the Attributes page (the Attributes tab in the Device Administration panel).

For more information on custom attributes, see the section on Custom Attributes.

To align custom attributes with a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Find the device that you want to align with a custom attribute. Click its wrench icon ().
Click the Attributes tab.
On the Attributes page, go to the Please Select field in the bottom-most row.
Select the custom attribute that you want to align with the device.
Enter a value in the Value field.

To align an extended custom attribute with a device, you must supply a value. You cannot align an extended custom attribute to a device and leave the value as "null".

Base custom attributes for devices are automatically aligned with each device in your Skylar One system. If the base custom attribute does not include a value for this device, the Value column displays "--". To assign a value to an "empty" base custom attribute, find the base custom attribute that you want to edit. Click its wrench icon (). Enter a value in the Value field.

Click the Save button.

Creating a New Extended Custom Attribute

You can create a new extended custom attribute from the Attributes page. The custom attribute is then aligned with the current device and available to be used by any device in your Skylar One system. To create a new extended custom attribute:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Find the device for which you want to create a new custom attribute. Click its wrench icon ().
Click the Attributes tab.
On the Attributes page, click the plus-sign icon () in the bottom row. Enter a value in the following fields:

Label. User-defined name for the custom attribute. This value appears in the user interface. If the value in this field does not comply with XML rules for names, Skylar One converts the value to a name that complies with XML rules and stores the converted value as the Internal Field Name for the custom attribute.

Names for custom attributes must conform to XML naming standards. The attribute name can contain any combination of alphanumeric characters, a period, a dash, a combining character or an extending character. If a value in the Internal Field Name column does not conform to XML standards, Skylar One replaces invalid characters with an underscore, the hexadecimal value of the invalid character, and an underscore. For example, "serial number" becomes "serial_X20_number".

Value Type. Specifies the type of value that the custom attribute stores. Choices are:

String. Non-numeric value
Integer. Numeric value

Value. The value that the custom attribute stores for this device.

Click the Save button.

Deleting an Extended Custom Attribute from a Device

You can delete an extended custom attribute from a device. When you delete the custom attribute, you remove the value from the custom attribute and remove the alignment between the custom attribute and the device.

You cannot delete a base custom attribute from the Attributes page. To delete a base custom attribute, you must go to the Custom Attribute Manager page (System > Manage > Custom Attributes).

To delete an extended custom attribute from a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Find the device for which you want to delete a custom attribute. Click its wrench icon ().
Click the Attributes tab.
On the Attributes page, find the extended custom attribute you want to delete. Click its delete icon ().
A dialog appears that asks you to confirm that you want to delete the value and remove the alignment between the custom attribute and the device.
Click the OK button.

Associating a Product SKU with the Device

A product stock keeping unit (SKU) describes a billable product or service and can be used later to create a billing policy. For more information on creating and editing product SKUs, see the Product Catalog page (Registry > Service Provider Utilities > Product Catalog). For more information on billing policies, see the Bandwidth Billing Policies page (Registry > Service Provider Utilities > Bandwidth Billing).

You can associate a product SKU with a device and then use a bandwidth billing policy to generate a bill that includes the device.

For more information on product SKUs and bandwidth billing policies, see the Business Services section.

To associate a product SKU with a device:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
On the Device Manager page, find the device that you want to associate with a product SKU. Click the wrench icon () for the device.
On the Device Properties page, select the Actions menu and choose Product Catalog.
The Product Catalog modal appears. In this modal, you can associate one or more product SKUs with the device:

To associate a product SKU with the device, in the Available Products pane, select one or more product SKUs.
To disassociate a product SKU from a device, in the Active Product Subscriptions pane, select one or more product SKUs.

Click the Save button.

Merging Devices

If your Skylar One system includes a physical device and a component device that both represent the same device, you can merge those devices into a single device for easier monitoring. Merging does not remove, replace, or add any data; merging just groups data together.

There are several benefits to merging physical and component devices:

The devices and their data (device fields, values, graphs, behaviors, and other user interface elements) consolidate into a single set of data for the device.
You reduce the number of duplicate events and administrative tasks.
Merged devices consume only a single device license.

For example, you might discover a virtual machine device component representing a server, and then later discover an IP-based device from the same server. To prevent duplicate events for the same server, minimize administrative tasks, and prevent a negative impact on your licensing by inflating the number of devices being monitored by Skylar One, you can merge the virtual machine component and the corresponding IP-based device into a single device.

You cannot merge a component device with a physical device that acts as the root device for a dynamic component map (DCM) tree.

When you merge a physical device and a component device, the component device no longer appears in the user interface. The physical device appears on the pages that previously displayed the component device. For example, the physical device appears instead of the component device on the Device Components page and the Component Map page. The physical device receives all existing and future data for both devices.

Merged devices can be unmerged back into individual devices, if needed.

You can merge only two individual devices together into a single merged device. To do so, you must have user permissions that allow merging and unmerging on both devices. For more information on user access permissions, see the section on Assigning Access Hooks.

When you merge devices, active events for the component device change to "cleared." The cleared events do not become associated with the physical device. If you unmerge the devices, you cannot move the cleared events back to the component device.

When you merge devices, the log data from each device also merges. You cannot unmerge the log data later.

Use consistent device hostnames to make device merging easier.

You can merge and unmerge devices on the Devices page. This workflow supports both individual and bulk operations. For more information, see Merging and Unmerging Devices from the Devices Page.

If you are using the classic Skylar One user interface, see Merging Individual Devices in the Classic User Interface to merge individual devices and Unmerging Individual Devices in the Classic User Interface to unmerge them. To merge or unmerge multiple devices at once in the classic Skylar One user interface, see Bulk Merging and Unmerging of Devices in the Classic User Interface.

Merging and Unmerging Devices from the Devices Page

You can merge or unmerge physical devices and component devices that represent the same device on the Devices page. You can select one device pair or multiple device pairs.

Merging Devices from the Devices Page

You can merge physical devices and component devices that represent the same device on the Merge Devices modal from the Devices page.

To open the Merge Devices modal:

Go to the Devices page.
Click the drop-down arrow next to the Add Devices button. Select Merge Devices. The Merge Devices modal appears.

The Merge Devices modal displays two tables: Physical Device and Component Device. Each table includes columns such as Device Name, IP Address, Device Category, Device Class, Device ID, and Organization, along with column filters to help you locate devices.

At the top of the Merge Devices modal, you can control how devices are matched using the fields displayed above the device tables. By default, in the Merge Devices modal, you can manually select the physical devices and component devices to merge. In this mode, Skylar One does not apply matching logic and does not show comparison criteria.

Optionally, you can enable Suggested Device Matches to allow Skylar One to automatically generate device merge suggestions based on selected matching criteria.

When Suggested Device Matches is not enabled, the modal displays the following matching fields:

Name
IP Address
Organization
Device Class

For each field, you can manually review and select one of the following options to define how the physical device and component device values are compared:

Ignore. Skylar One does not evaluate this criterion when generating suggested matches.
Match. Skylar One suggests device pairs only when the selected values on the physical device and component device are the same.
Does Not Match. Skylar One suggests device pairs only when the selected values on the physical device and component device are different.

When you enable Suggested Device Matches, the Merge Devices modal switches to an assisted matching mode and displays additional options that define how Skylar One generates merge suggestions. In this mode, Skylar One compares physical and component devices based on selected criteria and suggests device pairs that meet those conditions. In this view, additional matching fields become available:

Collection State
Collection Group

When Suggested Device Matches is enabled, the Merge Devices modal automatically preselects the suggested physical–component device pairs. You can review these selections and remove individual pairs before clicking Merge.

Skylar One uses the selected fields to automatically generate suggested physical–component device pairs. Fields set to Ignore do not affect matching. Fields set to Match or Does Not Match determine the suggested matches.

To merge one device pair or multiple device pairs:

From the Merge Devices modal, select one or more physical-component device pairs.
Review the selected pairs. Click the Merge button.

You can merge a single device pair or multiple device pairs in the same operation. To review previous merge activity, click View Merge Device Logs.

Unmerging Devices from the Devices Page

You can unmerge previously merged physical devices and component devices on the Unmerge Devices modal from the Devices page.

To open the Unmerge Devices modal:

Go to the Devices page.
Click the drop-down arrow button next to the Add Devices button and select Unmerge Devices. The Unmerge Devices modal appears.

The Unmerge Devices modal displays two tables: Physical Device and Component Device.

The Physical Device table includes columns such as Device Name, IP Address, Device Category, Device Class, and Device ID.
The Component Device table includes columns such as Device Name, Device Category, Device Class, Device ID, Merged Date, and Merged By. These columns indicate when the device was merged and the user who performed the merge.

To unmerge one device pair or multiple device pairs:

From the Unmerge Devices modal, select one or more merged device pairs.
Review the selected pairs, then click Unmerge.

You can unmerge a single device pair or multiple device pairs in the same operation. To review previous merge and unmerge activity, click View Merge Device Logs.

You can click the Merge Devices button to open the Merge Devices modal.

Merging Individual Devices in the Classic User Interface

If you have a small number of physical and component devices that you want to merge, you can merge each device pair individually.

If you have a large number of devices you want to merge, it might be more efficient to use the Bulk Merge feature, which is described in the Performing a Bulk Device Merge section.

The following instructions describe how to merge a physical device from the Device Manager page with a selected component device, but the process is the same when you merge a component device from the Device Manager page with a selected physical device.

To merge individual devices:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Click the wrench icon () for the physical device that you want to merge with a component device.
On the Device Properties page, click the Actions menu and then select Merge Device.
A list of component devices that you can merge with the physical device appears. Click the merge icon () for the component device you want to merge with the physical device. Information for the component device then displays in the Selected Device panel.
Click the Merge button. A dialog appears that asks you to confirm the merge.
Click the OK button.

To view an updated list of devices that includes your merged devices, click the Reset button on the Device Manager page.

Unmerging Individual Devices in the Classic User Interface

You can unmerge any pair of physical device and component device that are currently merged. When you unmerge devices, Skylar One does not delete any devices or device data. The devices separate into two individual devices.

If you have a large number of devices you want to unmerge, it might be more efficient to use the Bulk Unmerge feature, which is described in the Performing a Bulk Device Unmerge section.

The log data associated with the devices cannot be unmerged. After the devices are unmerged, all log data that was generated before the devices were unmerged is associated with the physical device.

For more information on unmerging a vanished device, see the section on unmerging vanished devices.

To unmerge individual devices:

Go to the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface).
Select the wrench icon () for the device that you want to unmerge.
On the Device Properties page, click the Actions menu, and then select Unmerge Device.
A dialog appears that asks you to confirm. Click the Unmerge button.

To view an updated list of devices that includes your unmerged devices, click the Reset button on the Device Manager page.

Performing Administrative Tasks for One or More Devices

The Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic user interface) contains a drop-down field in the lower right called Select Action. Use this field to apply an action to multiple devices at the same time.

To apply an action to multiple devices:

On the Device Manager page, select the checkbox for each device you want to apply the action to. To select all checkboxes for all devices, select the checkbox at the top of the page.

In the Select Action drop-down list, select one of the following actions:

Delete Devices. Deletes all selected devices from Skylar One. Tickets associated with the device are unlinked from the device, but are not deleted.
Modify by Template. Displays the Applying Template to Device page, where you can apply the settings in a device template to all selected devices. You can also make one-time changes to the template that apply only to the selected devices.
Clear Device Logs. Deletes data from the device's log files.
Create Asset Record. Automatically creates an asset record for the device. Skylar One automatically populates as many fields as possible, using retrieved data.
Schedule Maintenance. Leads to the Maintenance Schedule page. On this page, you can specify a date and time to put each selected device into "maintenance mode". During maintenance mode, Skylar One does not generate events about the selected devices. You can choose to enable or disable polling during maintenance mode. Even if you enable polling, Skylar One collects information from the selected devices but does not generate events for them.
Find Collection Label Duplicates. Leads to the Duplicates page. On this page, you can view a list of devices where a collection label has more than one presentation object aligned. From this page, you can manually align a single presentation object with a Collection Label for a device.
Change Collection State. Changes the status of the device in Skylar One. The choices are:

Active. Skylar One polls the device on a regular basis and updates the data displayed in Skylar One.
Disabled. Skylar One does not poll the device. Data displayed in Skylar One is not updated.

Change Maintenance Mode. Use these options to enable user maintenance and to disable both user maintenance and scheduled maintenance.

When a device is in User-Initiated-Maintenance, by default Skylar One does not generate events about the device. If you want to allow events during User-Initiated-Maintenance, you can specify which events to allow on the Behavior Settings (System > Settings > Behavior) page. You can choose to enable or disable polling. If you enable polling during User-Initiated-Maintenance, Skylar One collects information from the device but generates only the events you specified on the Behavior Settings page. By default, Skylar One does not generate any events. User-Initiated-Maintenance mode is not scheduled. You must manually enable User-Initiated-Maintenance to put a device into this mode. You must manually disable User-Initiated-Maintenance to turn off this mode for a device. User-Initiated-Maintenance Mode overrides scheduled maintenance for a device. Choices are:

Enabled with Collection. One or more devices are set to User-Initiated-Maintenance mode. During User-Initiated-Maintenance mode, Skylar One continues to poll the device.

Enabled without Collection. One or more devices are set to User-Initiated-Maintenance mode. During User-Initiated-Maintenance mode, Skylar One does not poll the device.
Disabled. User-Initiated-Maintenance mode is disabled for each selected device.

Change Collector Group. Changes the collector group used to collect data from the device. Select from the list of all collector groups in Skylar One. When you select a collector group, the collectors in that group poll each selected device. For All-In-One Appliances, you can select only the built-in collector group and any virtual collector groups.
Move To Organization. Associates a device with an organization. The list of choices includes all organizations in Skylar One.
Align SNMP Read Credential. This option applies the selected credential to all selected devices. The selected devices use the selected credential as their primary credential. Secondary credentials remain unchanged. Select from a list of SNMP Read credentials (defined in System > Manage > Credentials). The list includes only the credentials that you can use.
Add to Device Group. This option aligns the selected devices with the selected device group. The selected devices then appear on the Device Group Views page and inherit the properties of the device group, including scheduling, access, and visibility.
Align to Device Dashboard. This option aligns the selected devices with the selected device dashboard. The selected device dashboard appears as the default view on the Device Summary page.

Click the Go button.
The selected action applies to each selected device.

Shortcut Keys for the Device Administration Panel

When you click the wrench icon () for a device, you enter the Device Administration panel.

When you enter the Device Administration panel, you can use the following shortcut keys to navigate the tabbed pages and the entries in the Actions menu.

Page or Tab	Shortcut Keys
Administer Bookmarks page	Ctrl + Alt + B
Dynamic Application Collections page	Ctrl + Alt + C
Device Groups page	Ctrl + Alt + D
Guides page	Ctrl + Alt + G
Device Thresholds page	Ctrl + Alt + H
Device Interfaces page	Ctrl + Alt + I ("eye")
Device Logs & Messages page	Ctrl + Alt + L
Monitoring Policies page	Ctrl + Alt + M
Notes & Attachments page	Ctrl + Alt + N
Device Toolbox page	Ctrl + Alt + O ("oh")
Device Properties page	Ctrl + Alt + P
Maintenance Schedule page	Ctrl + Alt + S
Ticket History page	Ctrl + Alt + T
Resource Usage page	Ctrl + Alt + U
Exit Device Administration panel	Ctrl + Alt + X
Device Properties page	Ctrl + Alt + . ("period")
Ticket Editor page	Ctrl + Alt + Enter