--- title: "About the Network Partition" slug: "about-the-network-partition" tags: ["network partition", "partitioning", "Legacy Orchestrator", "Network Partitioning"] updated: 2026-05-29T18:52:07Z published: 2026-05-29T18:52:07Z canonical: "docs.crossworkassurance.cisco.com/about-the-network-partition" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt > Use this file to discover all available pages before exploring further. # About the Network Partition Partition is a grouping of managed elements that will be given a name. Legacy Orchestrator’s network partitioning functionality allows you to identify resources that a particular user (or group of users) is able to view in the system. Users will be limited via a network partition to see their specific resources. **Network Partitions Page** ![24.09_About the Network Partition_1.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/24.09_About%20the%20Network%20Partition_1.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A52%3A05Z&se=2026-11-22T20%3A52%3A05Z&sr=b&sp=r&sig=rx1LnhalOWGGeoKTert8gSY%2FDpN9YdhXX1q9wdguBqE%3D) Select **Network Partitions** in the left pane to create and configure a set of resources in the system that can then be identified as a partition. Once configured, the admin user can assign one or multiple users to this partition. --- ***Notes**:* *Only the Admin-level users can create, edit and delete partition configurations. Only the Admin-lever users can assign the other user roles to a partition.* *A user who is not assigned to any partition will be granted full network resources.* *One or multiple users can be assigned to one or multiple partitions.* *Partitioning is not possible with modules. Only the modules that belong to one of the Cisco® Crosswork Assurance Sensor Control of the user's assigned partitions are displayed.* --- ## Impact of Networking Partitioning The following section explains how network partitioning affects various Legacy Orchestrator functions. ### Devices - Devices that belong to one of the user's assigned partitions are displayed. This applies to both the **Firmware** page and the **Backup & restores** page. - Only the Modules that belong to one of the user’s Assurance Sensor Contros assigned to partitions are displayed. ### Commission - Only devices in a user partition can be selected throughout job executor creation and network flow executors. Similarly, only all devices belonging to a network partition of a user are permitted to be executed in an executor. - A user is able to see all the assigned devices as well as details of all the devices from the previous run of job executors and flow executors, even devices outside of this user partitioning scope. - The executors only work with devices that belong to a user’s network partitions although these executors use ME Reference Datasets. - An error message related to out-of-scope devices will appear and all out-of-scope devices will appear while using **Dry run** button in a previously configured executor with any devices not belonging to user's network partition. - During scheduled jobs execution, it will be performed with all devices that are assigned in this job. - All devices that are automatically added into Legacy Orchestrator by Discovery Trigger will not be assigned to any partition. Only admin user and users with no network partition restrictions will be able to see them. ### Inventory - Inventory queries are limited to the elements and modules in a user’s network partition and the device filter will only display devices from the current user’s network partitions. - Some behaviors similar to the commission section will occur during an export execution: - If the "All devices" checkbox is selected while configuring the export: ### Service performance - The tests and test results of modules and devices are only visible to the user if they are in this user’s network partition. - While creating a test: - If a module or element is a far-end element that has an L3 Two-Way loopback required, the far-end loopback will be bypassed if that element is not in the user’s partition. ### Collection Only devices belong this user’s network partition are shown in the Device Configuration and Reporting Status tabs. ### Sessions - Only sessions from the sender belonging to this user's network partition are displayed. - While creating a session: ### REST API - Legacy Orchestrator supports creating, editing or deleting Y.1564 and RFC 2544 configurations via API. - The user can use RESTfull API to search information related to resources (devices, modules) belonging to their network partition. - Job executors will not start and an error message related to out-of-scope devices will be returned if there are any assigned devices that do not belong to this user's network partition. This behavior will be the same with all manager NBI operations (primarily endpoints and sessions). - Concerning SLA: ### RADIUS Authenticated users have the same privileges as Local users: - Local admin and RADIUS admin users are able to configure the network partition, but cannot be assigned to a partition (will be hidden from the partition view). - The Local and RADIUS users that have other roles such as Operator, WS, Viewer, and FW Management can be assigned to a partition (will be displayed in the partition view). **© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)