How to Copy and Apply Profiles in MCS

uim203
This article describes the best practices for copying and applying profiles in Monitoring Configuration Services (MCS). This document also gives some business use case examples. The examples demonstrate best practices.
3
2
Using MCS, you can copy a device or a group profile (the source) and apply the copied profile to a device or a group profile (the target). When you apply a profile at the group level, MCS applies this profile to all devices within the group. Device level configuration overrides the group level configuration. When you copy and apply a profile, MCS analyzes the source against the target. What MCS does after analyzing the source against the target depends on whether the group has a previously configured group profile.
Copy and Apply a Profile
This procedure includes high-level steps that help you understand how you can copy and apply profiles.
For detailed information about specific scenarios and best practices, see the Best Practices and Examples sections.
Follow these steps:
  1. From the Inventory view or Group view, navigate to the appropriate group or device.
  2. Click the Monitoring Config icon (gear icon) available in the top-right corner.
  3. Locate the group or device profile (as applicable) that you want to copy and apply.
    Copy MCS profiles
  4. Click the
    Copy Profile
    option.
    Copy MCS profiles
    The
    Copy Profile
    dialog opens.
  5. Select whether you want to apply the profile to a group or device.
    Copy MCS profiles
    Depending on your selection, the
    Search Device Or Group
    field is populated with a list of related devices or groups. Click the field to view the list
    Copy MCS profiles
  6. From the list, select the required group or device (as applicable) where you want to apply the profile.
  7. Click the
    Copy Profile
    button.
    The profile is applied to the intended device or group.
Best Practices
When using MCS, it is most efficient to first create a device profile. Then, you can test it and can modify it as needed. Only copy and apply tested device profiles to a device or group in a production environment. When you monitor with MCS, we recommend that you follow this process:
  1. Create and configure a device profile.
  2. Modify and test the device profile in an isolated test environment.
  3. Determine how you want to group your devices.
  4. Copy and apply the device profile to the desired devices or groups.
  5. Repeat steps 1-4 as you make configuration changes to your production environment.
Examples
These examples show some common use cases.
Copy and Apply a Device Profile to a Group (Not Having a Group Profile)
When you copy and apply a profile to a group that does not have a group profile:
  • The applied profile becomes the group profile.
  • All devices inherit the group profile.
  • The group profile is the effective configuration for all the devices in the group.
This enables you to start with one device profile and then to standardize it for a group profile.
In this example, you are setting up a new call center. You create a group that is named Call Center 2. The Call Center 2 group does not have a group profile.
In your Call Center 2 group, you have three devices:
  • Accounts 2
    The device Accounts 2 does not have a device profile.
  • Brokerage 2
    The device Brokerage 2 has a device profile.
  • Fraud 2
    The device Fraud 2 does not have a device profile.
You want to create a device profile in your test environment and, after testing it, apply it to the Call Center 2 group.
Following best practices, you use a test server to develop the new CPU Monitor device profile. In this example, we assume that you have a test server that is named Fraud Test 2.
Follow these steps
:
  1. Create a CPU Monitor device profile on Fraud Test 2.
  2. Modify and test the CPU Monitor device profile on Fraud Test 2.
  3. Copy the CPU Monitor device profile from Fraud Test 2.
  4. Apply the CPU Monitor device profile to the Call Center 2 group profile in your production environment.
When you apply the CPU Monitor device profile to the Call Center 2 group in your production environment:
  • The source, the CPU Monitor device profile from Fraud Test 2, becomes the group profile for the Call Center 2 group.
  • The Accounts 2 device, which did not have a device profile, now inherits the group profile for the Call Center 2 group.
  • The Brokerage 2 device, which had a device profile, retains the device profile.
  • The Fraud 2 device, which did not have a device profile, now inherits the Call Center 2 group profile.
Copy and Apply a Device Profile to a Device (Inheriting a Group Profile)
In this example, you have a group that is named Factory. The Factory group has a CPU Monitor group profile. In the Factory group you have two devices:
  • Manufacturing
    The Manufacturing device has a CPU Monitor device profile that it inherits from the Factory group profile. You have not modified the inherited profile for Manufacturing. It is therefore identical to the Factory group profile.
  • Distributing
    The Distributing device has a CPU Monitor device profile that it inherits from the Factory group profile. You have not modified the inherited profile for Manufacturing. It is therefore identical to the Factory group profile.
You want to modify the configuration for the Distributing device. You want the Distributing device profile to include metrics from the Factory group profile and more metrics. You also plan to add many more devices to the Factory group. You want these many devices to inherit the configuration from the Factory group profile.
Following best practices, you:
  1. Use a test server to develop the new CPU Monitor device profile for the Distributing device.
    In this example, we assume that you have a test server that is named Distributing Test.
  2. Copy the CPU Monitor device profile from the Distributing device in your production environment.
  3. Apply the CPU Monitor device profile to the Distributing Test device in your test environment.
  4. Modify and test the CPU Monitor device profile on Distributing Test.
  5. Copy the CPU Monitor device profile from Distributing Test.
  6. Apply the CPU Monitor device profile to the Distributing device in your production environment.
When you apply CPU Monitor device profile to the Distribution device in your production environment:
  • The Distributing Test profile becomes the device profile for only the Distributing device. It affects no other devices within the group.
  • The effective profile for the Distributing device is a merge of the device profile and the Factory group profile. Device level configuration takes precedence over group level configuration. Therefore:
    • MCS ignores the data in any field that is identical for the group profile and the new device profile.
    • MCS overrides the data in any field where there is a difference between the group profile and the new device profile.
Copy and Apply a Device Profile to a Device (Not Inheriting a Group Profile)
In this example, you have a group that is named Development. The Development group does not have a group profile. Within the Development group, you have two devices.
  • Engineering
    The Engineering device does not have a device profile.
  • QA
    The QA device does not have a device profile.
You want to create a CPU Monitor device profile for the QA device. You want to include a few metrics for the QA device that you do not want to apply to any other device in the Development group. You also plan to add many more devices to the Development group. You do not want these many devices to use the QA device profile.
You decide to create, test, and apply a CPU Monitor device profile to the QA device.
Following best practices, you:
  1. Use a test server to develop the new CPU Monitor device profile for the QA device.
    In this example, we assume that you have a test server that is named QA Test.
  2. Create a CPU Monitor device profile on QA Test.
  3. Modify and test the device profile on QA Test.
  4. Copy the device profile from QA Test.
  5. Apply the device profile to the QA device in your production environment.
When you apply the device profile to the QA device in your production environment: 
  • The QA Test profile becomes the device profile for only the QA device.
  • The Engineering device still does not have a device profile.
  • The Development group still does not have a group profile.