---
title: "Modifying a Configuration - icom Data Suite"
slug: "modifying-a-configuration-en"
updated: 2024-10-01T15:36:40Z
published: 2024-10-01T15:36:40Z
canonical: "docs.insys-icom.com/modifying-a-configuration-en"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Modifying a Configuration - icom Data Suite

This Configuration Guide shows how to download the configuration, modify it and upload it again remotely using the Command Shell in Cumulocity Cloud or Telekom Cloud of Things.

## Situation

The configuration is stored in a profile. It might be necessary to modify the configuration from remote. The profile with the configuration can be output in the Command Shell for viewing and/or editing. An edited profile can be written to the router using the Command Shell.

## Solution

It is prerequisite that you have a cloud service account. The router must be registered in the cloud service. Refer to the Configuration Guide [Registering and Sending a Value to the Cumulocity Cloud](/kb/docs/en/cumulocity-cloud-registering-and-sending-a-value-en) to see how to register a router in the Cumulocity Cloud. The version of the icom Data Suite must be 1.3 or later.

1. Log in to your Cumulocity Cloud account.
2. Click on *Other applications* () in the top right corner and select *Device management*.
3. Click on *All devices* and select your router in the list of all devices.
4. Click on *Shell* ()
5. In the *>_* *Command* field, enter: `M3.administration.profiles.print` (this command outputs the complete opened profile)
6. Click on *Execute* to output the profile.
7. Copy the complete output to a text editor.
8. Edit the commands you want to modify or add additional commands to the profile.
9. Remove the string `returned:` in front of and behind the profile text.
10. Insert the line `<M3_Block>` at the beginning of the profile text (this indicates the Command Shell that a series of commands will follow that are to be directed to the specified device (here M3, i.e. the router)).
11. Add the line `administration.profiles.activate` to the end of the profile text (this command activates the opened profile).
12. Add the line `<M3_Block_END>` to the end of the profile text (this indicates the Command Shell that the series of commands to the specified device ends here).
13. Copy the complete profile text to the *>_* *Command* field now.
14. Click on *Execute*.

Profile text example

```plaintext
<M3_Block>
returned: interfaces.dsl3.ip_address.delete=all
interfaces.net1.ip_address.delete=all
…​
…​
…​
administration.update.server[2].download_precondition=header_and_filename_changed
administration.profiles.activate
<M3_Block_END>
returned:
```

> [!NOTE]
> Please note!
> 
> The prefix `M3.` determines that the commands are sent to the **router**. The prefix `IDS.` would determine that the commands are sent to the icom Data Suite. To modify the configuration of the **icom Data Suite**, replace `M3` by `IDS` in the example above (also for the block delimiters).

## Troubleshooting

- The commands entered in the Command Shell are case-sensitive.