Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Extensible Attribute rule
  • Subnet rule
  • Geography rule

Image Removed
1044NIOS Administrator Guide (Rev. A)NIOS 8.1
Configuring Topology Rules and Rulesets
The destination for a topology ruleset is either a server or a pool. An LBDN can use only topology rulesets with a pool as the destination. A pool can use only topology rulesets with a server as the destination.
You can also use CSV import to import rules into NIOS.

Anchor
Defining Topology Rulesets
Defining Topology Rulesets
Anchor
bookmark2098
bookmark2098
Anchor
bookmark2099
bookmark2099
Defining Topology Rulesets

...

An example of valid source types:

Continent

Country

Subdivision

City

Any

Canada

Any

Vancouver

Any

Any

Any

Vancouver

North America

Any

Any

Vancouver

North America

USA

Washington

Vancouver


  • When rules have multiple source conditions, the client must match all conditions for the rule to execute.
  • A ruleset may have multiple subnet rules and the subnets may overlap. Similarly, a ruleset may have multiple geography rules and the matches may overlap. Similarly, a ruleset may have multiple extensible attribute rules and the matches may overlap. During the querying process, the rules in a topology ruleset are evaluated in order. For example, if you configure subnet rules where #1 is 10.10.0.0/16 and #2 is 10.0.0.0/8, both are considered valid in the appliance.

...

  1. From the Data Management tab, select the DNS tab -> Traffic Control tab, and then click Manage Topology Rulesets in the Toolbar.
  2. In the Topology Manager window, click the Add icon.
  3. In the Ruleset wizard that appears, complete the following:
    • Name: Enter a name for the ruleset.

...

    • .

...

    • Destination Type: Select a destination type, Pool or Server. Rulesets with the Pool destination type can only be used by LBDNs. Rulesets with the Server destination type can only be used by pools. You cannot change the destination type if the ruleset contains any rules.
    • Comment: Enter additional information about the ruleset.
    • Rules: You can define multiple extensible attribute rules, subnet rules, and geography rules in the ruleset. Click the arrow next to the Add icon and select either Extensible Attribute Rule, Subnet Rule, or Geography Rule.
      • When you select Extensible Attribute Rule, Grid Manager displays the following:
        • Source Type: Define up to four extensible attributes to use as the source type for the EA topology ruleset. To define extensible attribute source types for the topology rules, see Configuring Grid DNS Traffic Control Properties .
          Note that "Any" matches any value. There must be at least one source type with a specific value (the value is not "Any").
          When a source type uses "does not equal" as the operator, it must be the lowest level source type (most specific). For example, with Continent/Country/Subdivision/City, City is the most specific source type.
        • Destination: Click Select to select a destination. The appliance displays the DTC Pool Selector dialog box when you have selected the Pool destination type and displays DTC Server Selector dialog box when you have selected the Server destination type. Click a specific pool or server to select it. Note that if there is only one pool or server, no dialog box is displayed when selecting the destination.

Click Add to add the source. The appliance displays the following information in the Rules table:

        • Source: The values of extensible attributes that you specified.
        • Destination: The destination that you selected.
        • ValidSource: After you save the ruleset, the value is set to Yes if the extensible attributes exist in the EA database.

...

Note: The source must be valid when creating a ruleset. It can become invalid when a new topology database no longer contains the source.

...

        • Order: Displays the order of the rule in the ruleset.
      • When you select SubnetRule, Grid Manager displays the following:
        • SourceSubnet: Select a value from the drop-down list. You can either select equals or doesnotequal and specify a subnet IP address or click Select and choose a network from the NetworkSelector dialog box.
          Note that "Any" matches any value. There must be at least one source subnet with a specific value (the value is not "Any").
          When a source subnet uses "does not equal" as the operator, it must be the lowest level source subnet (most specific).
        • Destination: Click Select to select a destination. The appliance displays the DTCPoolSelector dialog box when you have selected the Pool destination type and displays the DTCServerSelector dialog box when you have selected the Server destination type. Click a specific pool or server to select it. Note that if there is only one pool or server created, no dialog box is displayed when selecting the destination.

Click Add to add the source. The appliance displays the following information in the Rules table:

        • Source: The subnet address that you specified.
        • Destination: The destination that you selected.
        • ValidSource: For a subnet rule, the rule is always marked as valid after you save the ruleset.
        • Order: Displays the order of the rule in the ruleset.
      • When you select Geography Rule, Grid Manager displays the following:

...

        • Source Type: Select a source type.
        • Continent: Select a continent from the drop-down list. You can also enter the first few characters of the continent to match an item in the database.
        • Country: Select a country from the drop-down list. You can also enter the first few characters of the country to match an item in the database.
        • Subdivision: Select a subdivision from the drop-down list. You can also enter the first few characters of the subdivision to match an item in the database.
        • City: Select a city from the drop-down list. You can also enter the first few characters of the city to match an item in the database. The drop-down list has paging controls to page through the available values.
        • Destination: Click Select to select a destination. The appliance displays the DTCPoolSelector dialog box when you have selected the Pool destination type and the displays DTCServerSelector dialog box when you have selected the Server destination type. Click a specific pool or server to select it. Note that if there is only one pool or server created, no dialog box is displayed when selecting the destination.

Click Add to add the source. The appliance displays the following information in the Rules table:

        • Source: The subnet address that you specified.
        • Destination: The destination that you selected.
        • ValidSource: After you save the ruleset, the value is set to Yes if the labels exist in the MaxMind location database.
        • Order: Displays the order of the rule in the ruleset.
      • Default destination if none of the above rules match (optional): Click Select to select the default destination if none of the above rules match. The appliance displays the DTCPoolSelector dialog box when you have selected the Pool destination type and displays the DTCServerSelector dialog box when you have selected the Server destination type. Click a specific pool or server to select it. You can click Clear to remove the selected pool or server. Note that you can select a default destination even if there are no rules defined in the Rules table.

4. If necessary, modify the order of rules in the table. You can do so by editing the value in the Order column or using the arrows on the left side of the table.

       5. Click Next.

       6. Define the extensible attributes. For information, see Using Extensible Attributes.

7. Click Next to schedule change. In the ScheduleChange panel, click Now to immediately execute this task. Or click Later to schedule this task, and then specify a date, time, and time zone.

       8. Click Save&Close.

...

Note: After making changes to the extensible attributes, you may need to rebuild the topology EA database. For more information, see Rebuilding EA Database.

...

Anchor
Viewing Topology Rulesets
Viewing Topology Rulesets
Anchor
bookmark2100
bookmark2100
Viewing Topology Rulesets

...

  • Add new rulesets. To add a new ruleset, click the Add icon. For more information, see Defining Topology Rulesets5.
  • Edit a ruleset by clicking the check box next to the ruleset name and clicking the Edit icon. You can modify the following in the Ruleset editor:
    • In the General Basic tab, you can do the following:

...

    • Add new rules to the ruleset. Click the arrow next to the Add icon and select either Extensible Attribute Rule, Subnet Rule, or Geography Rule. For more information, see Defining Topology Rulesets on page 1045.
    • Modify rules in the ruleset. To edit an existing rule, select the check box of the required rule in the Rules table and click the Edit icon. When finished with editing, click Save above the Rules table. For more information, see Defining Topology Rulesets .
    • Delete existing rules from the ruleset. Select the check box of the required rule in the Rules table and click the Delete icon.



Note: You can modify the destination type only if there are no rules in the ruleset.

    • In the Extensible Attributes tab, you can add new or edit existing extensible attributes. For information, see

...

{Product}{Content}{Blocks-or-Locations}-{version-or-localization}.csv. Only the three CSV files matching these patterns are suitable for the import:
Image Modified
1048NIOS Administrator Guide (Rev. A)NIOS 8.1
Configuring Topology Rules and Rulesets

{Product}-{Content}-Blocks-IPv4.csv
{Product}-{Content}-Blocks-IPv6.csv
{Product}-{Content}-Locations-en.csv For example:
GeoLite2-City-Blocks-IPv4.csv GeoLite2-City-Blocks-IPv6.csv GeoLite2-City-Locations-ru.csv or
GeoIP2-Country-Blocks-IPv4.csv GeoIP2-Country-Blocks-IPv6.csv GeoIP2-Country-Locations-en.csv where
"GeoLite2" and "GeoIP2" correspond to {Product} "City" and "Country" correspond to {Content} "IPv4" and "IPv6" correspond to {version}
"ru" and "en" correspond to {localization}

Note: The Locations file and at least one of the Blocks files must exist or the import fails. Also, all of these files must have identical {Product}-{Content} pairs or the import fails. You can use a ready-to-use MaxMind location database as an example.

  1. You can add multiple CSV files for different localizations to your ZIP file. Use the following naming pattern:

...

  1. From the Data Management tab, select the DNS tab, and then select the Traffic Control tab.
  2. In the Toolbar, click the arrow next to the Topology Database and select Rebuild EA Database -> Rebuild or Schedule Rebuild.
  3. In the Rebuild EA Database dialog box, select Yes to rebuild the database or No to discard the rebuild. To schedule the rebuild task, in the Rebuild EA Database Schedule dialog box, specify a date, time, and time zone.



Image Modified
NIOS 8.1NIOS Administrator Guide (Rev. A) 1049
Managing DNS Traffic Control

To view the current version of the EA database, click Topology Database -> Current Version in the Toolbar. Grid Manager displays the database build date and its last rebuild status in the Extensible Attributes section.

Note: The latest database version may not be deployed on all DTC members. To view the current deployed versions, select Data Management -> DNS -> Members.