> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/hardware/new-hardware/creating-a-1-plus-1-group.md).

# Creating a 1+1 Group

> **Applies to:** Tmedia 3.0, 3.2, 3.3

A 1+1 group identifies the two Tmedia hardware devices operating together to provide 1+1 backup protection. One device is identified as the primary hardware device, while the other device is identified as the backup hardware device. To create a 1+1 group, use the Tmedia [Web Portal](/tmedia-documentation/other-pages/other/web-portal.md).

**To create a 1+1 group:**

1- Click **1+1** in the navigation panel

![Create1and1Group 0 B](https://docs.telcobridges.com/w/images/0/02/Create1and1Group_0_B.png)

2- Click **Create New 1+1 Group**

![Create1and1Group 1 B](https://docs.telcobridges.com/w/images/9/98/Create1and1Group_1_B.png)

3- Enter the serial numbers of the primary and 1+1 backup hardware devices.

* Provide a name for the 1+1 group.
* Select the **serial number** of the primary hardware device. (This field may already be filled.)
* Select the **serial number** of the 1+1 backup hardware device.
* Set **Auto switch-back** to cause an automatic switch back to the original primary hardware device when it becomes available. If the field is clear (not checked), then a switch back to the original device will occur only after a manual reboot of the system.
* Click **Create**

![Create1and1Group 2 B](https://docs.telcobridges.com/w/images/b/b8/Create1and1Group_2_B.png)

4- Verify that the newly added 1+1 group appears in the **1+1 Groups** list.

![Create1and1Group 3 B](https://docs.telcobridges.com/w/images/c/c7/Create1and1Group_3_B.png)

**Path**

```
/configurations/@[configuration_name]/np1_groups/@[np1Group_name]
```

**Parameters (text)**

```
/configurations/Sylvain/np1_groups/One_PLUS_ONE_GROUP
auto_switch_back          = false
backup_unit               = "@[hardware_name]"
name                      = "@[np1Group_name]"
primary_np1_patch_panel   = "NONE"
primary_unit              = "@[hardware_name]"
secondary_np1_patch_panel = "NONE"
```

**Parameters (json)**

```
{
  "auto_switch_back" : false,
  "backup_unit" : "@[hardware_name]",
  "name" : "@[np1Group_name]",
  "primary_np1_patch_panel" : "NONE",
  "primary_unit" : "@[hardware_name]",
  "secondary_np1_patch_panel" : "NONE"
}
```

### List of Parameters

* [Name](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Primary Unit](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware#p)
* [1+1 Backup Unit](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/hardware)
* [Auto Switch-Back](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/tdm#a)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/hardware/new-hardware/creating-a-1-plus-1-group.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.