{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":48086,"path":"servicenow-platform/mid-server/mid-servers-auto-assignment.md","title":"Using MID Server IP range auto-assignment","bundle":null,"doc_type":null,"release":"australia","body":"\n# Using MID Server IP range auto-assignment\n\nDiscovery Quick Start can automatically assign ranges of IP addresses, called subnets, to qualified MID Servers. This subnet auto-assignment requires SNMP credentials for read-only access to routers Discovery uses. The Automation Status Set form shows summary details of subnet Discoveries and the IP range assignments for associated MID Servers.\n\n<table id=\"table_gvt_qs4_nhb\"><tbody><tr><td>\n\n![Setup indicator for configuration phase](../image/ProgressBarConfig.png)\n\n</td></tr></tbody>\n</table>To be automatically assigned to a subnet, a MID Server must be:\n\n-   In a running **\\(Up\\)** state.\n-   Successfully validated.\n-   Able to access one or more subnets in your network.\n\nThe subnet assignments that the instance makes for your MID Servers are stored in the Automation Status Set \\[automation\\_status\\_set\\] table. For details about MID Server auto-assignment, see [Discovery Quick Start](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/discovery-quick-start.md).\n\n**Important:** You must auto-assign at least one MID Server to create a schedule automatically.\n\n**Parent Topic:**[Configuring MID Servers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/mid-server/c_MIDServerConfiguration.md)\n\n## Required SNMP OIDs for MID Server IP range auto-assignment\n\nCustomers who use network service providers must request specific SNMP access to use MID Server IP range auto-assignment.\n\nIP range auto-assignment requires SNMP credentials for read-only access to all routers that Discovery uses to identify subnets. In addition, your service provider must grant the following SNMPWALK access:\n\n-   iso.org.dod.internet.mgmt.mib-2.ip.ipRouteTable \\(1.3.6.1.2.1.4.21\\)\n    -   ipRouteDest \\(1.3.6.1.2.1.4.21.1.1\\)\n    -   ipRouteNextHop \\(1.3.6.1.2.1.4.21.1.7\\)\n    -   ipRouteType \\(1.3.6.1.2.1.4.21.1.8\\)\n    -   ipRouteMask \\(1.3.6.1.2.1.4.21.1.11\\)\n-   iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable \\(1.3.6.1.2.1.4.24.4\\)\n    -   ipCidrRouteDest \\(1.3.6.1.2.1.4.24.4.1.1\\)\n    -   ipCidrRouteMask \\(1.3.6.1.2.1.4.24.4.1.2\\)\n    -   ipCidrRouteNextHop \\(1.3.6.1.2.1.4.24.4.1.4\\)\n    -   ipCidrRouteType \\(1.3.6.1.2.1.4.24.4.1.6\\)\n\n## View automation status sets and IP range assignments\n\nThe Automation Status Set form shows summary details of a subnet Discovery and the subsequent IP range assignments for MID Servers selected for automatic subnet assignment.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1.  Navigate to **All** &gt; **MID Server** &gt; **Automation Status Sets**.\n\n2.  Select a status record for a subnet Discovery you want to view.\n\n    The form contains read-only status information about the selected Discovery, the subnets found, and the range assignment process for the MID Servers you selected for auto assignment.\n\n    **Important:** IP ranges assigned manually prior to using auto-assignment in the [Discovery Quick Start](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/discovery-quick-start.md) are affected as follows:\n\n    -   Individual IP ranges are retained and appended to the ranges assigned automatically by the system for the designated MID Server.\n    -   If the MID Server was configured with the **ALL** ranges selection, the auto-assignment feature overwrites that designation with the ranges it finds.\n    \\[Omitted image \"AutomationStatusSet.png\"\\] Alt text: Automation Status Set form\n\n3.  Select the **Subnets Discovered** related list to view the list of subnets available for assignment.\n\n    \\[Omitted image \"SubnetsDiscovered.png\"\\] Alt text: Subnets Discovered\n\n4.  Select the **IP Range Assignments** related list to view the IP ranges that were assigned to a MID Server.\n\n    **Warning:** IP ranges identified by Discovery are stored in the IP collection \\[ip\\_address\\_collection\\] table, which is only used for MID Server IP range auto-assignment in the Jakarta release. This table is intended for future development and **should not** be used in any customizations, including column additions, business rules, or scripting actions.\n\n    \\[Omitted image \"IPRangeAssignments.png\"\\] Alt text: IP range assignments\n\n\n"}}