Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Paris Now Platform Capabilities Now Platform capabilities MID Server Configuring MID Servers Using MID Server IP range auto-assignment

    Using MID Server IP range auto-assignment

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Using MID Server IP range auto-assignment

    Discovery 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.

    Setup indicator for configuration phaseEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server securityEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server security
    To be automatically assigned to a subnet, a MID Server must be:
    • In a running (Up) state.
    • Successfully validated.
    • Able to access one or more subnets in your network.
    The 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.
    Important: You must auto-assign at least one MID Server to create a schedule automatically.

    Required SNMP OIDs for MID Server IP range auto-assignment

    Customers who use network service providers must request specific SNMP access to use MID Server IP range auto-assignment.

    IP 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:

    • iso.org.dod.internet.mgmt.mib-2.ip.ipRouteTable (1.3.6.1.2.1.4.21)
      • ipRouteDest (1.3.6.1.2.1.4.21.1.1)
      • ipRouteNextHop (1.3.6.1.2.1.4.21.1.7)
      • ipRouteType (1.3.6.1.2.1.4.21.1.8)
      • ipRouteMask (1.3.6.1.2.1.4.21.1.11)
    • iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable (1.3.6.1.2.1.4.24.4)
      • ipCidrRouteDest (1.3.6.1.2.1.4.24.4.1.1)
      • ipCidrRouteMask (1.3.6.1.2.1.4.24.4.1.2)
      • ipCidrRouteNextHop (1.3.6.1.2.1.4.24.4.1.4)
      • ipCidrRouteType (1.3.6.1.2.1.4.24.4.1.6)

    View automation status sets and IP range assignments

    The 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.

    Before you begin

    Role required: admin

    Procedure

    1. Navigate to MID Server > Automation Status Sets.
    2. Select a status record for a subnet Discovery you want to view.
      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.
      Important: IP ranges assigned manually prior to using auto-assignment in the Discovery Quick Start are affected as follows:
      • Individual IP ranges are retained and appended to the ranges assigned automatically by the system for the designated MID Server.
      • If the MID Server was configured with the ALL ranges selection, the auto-assignment feature overwrites that designation with the ranges it finds.
      Figure 1. Automation Status Set form
      Automation Status Set form
    3. Select the Subnets Discovered related list to view the list of subnets available for assignment.
      Subnets Discovered
    4. Select the IP Range Assignments related list to view the IP ranges that were assigned to a MID Server.
      Caution: 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.
      IP range assignments
    Related concepts
    • MID Server Configuration Home
    • MID Server Reference
    Related reference
    • MID Server Issues Home

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Using MID Server IP range auto-assignment

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Using MID Server IP range auto-assignment

      Discovery 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.

      Setup indicator for configuration phaseEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server securityEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server security
      To be automatically assigned to a subnet, a MID Server must be:
      • In a running (Up) state.
      • Successfully validated.
      • Able to access one or more subnets in your network.
      The 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.
      Important: You must auto-assign at least one MID Server to create a schedule automatically.

      Required SNMP OIDs for MID Server IP range auto-assignment

      Customers who use network service providers must request specific SNMP access to use MID Server IP range auto-assignment.

      IP 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:

      • iso.org.dod.internet.mgmt.mib-2.ip.ipRouteTable (1.3.6.1.2.1.4.21)
        • ipRouteDest (1.3.6.1.2.1.4.21.1.1)
        • ipRouteNextHop (1.3.6.1.2.1.4.21.1.7)
        • ipRouteType (1.3.6.1.2.1.4.21.1.8)
        • ipRouteMask (1.3.6.1.2.1.4.21.1.11)
      • iso.org.dod.internet.mgmt.mib-2.ip.ipForward.ipCidrRouteTable (1.3.6.1.2.1.4.24.4)
        • ipCidrRouteDest (1.3.6.1.2.1.4.24.4.1.1)
        • ipCidrRouteMask (1.3.6.1.2.1.4.24.4.1.2)
        • ipCidrRouteNextHop (1.3.6.1.2.1.4.24.4.1.4)
        • ipCidrRouteType (1.3.6.1.2.1.4.24.4.1.6)

      View automation status sets and IP range assignments

      The 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.

      Before you begin

      Role required: admin

      Procedure

      1. Navigate to MID Server > Automation Status Sets.
      2. Select a status record for a subnet Discovery you want to view.
        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.
        Important: IP ranges assigned manually prior to using auto-assignment in the Discovery Quick Start are affected as follows:
        • Individual IP ranges are retained and appended to the ranges assigned automatically by the system for the designated MID Server.
        • If the MID Server was configured with the ALL ranges selection, the auto-assignment feature overwrites that designation with the ranges it finds.
        Figure 1. Automation Status Set form
        Automation Status Set form
      3. Select the Subnets Discovered related list to view the list of subnets available for assignment.
        Subnets Discovered
      4. Select the IP Range Assignments related list to view the IP ranges that were assigned to a MID Server.
        Caution: 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.
        IP range assignments
      Related concepts
      • MID Server Configuration Home
      • MID Server Reference
      Related reference
      • MID Server Issues Home

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login