Creating Coverage Zone Files

Size: px

Start display at page:

Download "Creating Coverage Zone Files"

Amice Willis
5 years ago
Views:

APPENDIXC The following sections describe the Coverage Zone file elements and provide several Coverage Zone file examples: Coverage Zone File Elements, page C-1 Zero-IP Based Configuration, page C-2

1 APPENDIXC The following sections describe the Coverage Zone file elements and provide several Coverage Zone file examples: Coverage Zone File Elements, page C-1 Zero-IP Based Configuration, page C-2 Coverage Zone XML Schema, page C-3 Coverage Zone File Examples, page C-6 Tip For information about importing or uploading a Coverage Zone file, see the Coverage Zone File Registration section on page For more information about Coverage Zone files, see the Coverage Zone File section on page Coverage Zone File Elements A Coverage Zone file is an XML file used to specify a user-defined coverage zone. In this release of ECDS, the Coverage Zone file supports different tags to support network and subnet proximity configurations. In addition to the coverage zone information, two optional elements are created for documentation purposes: Revision value to specify the version of the Coverage Zone file Customer name Note The coverage zone file is limited to 40,000 entries. Coverage Zone files can be created using any ASCII text-editing tool. You can use a single coverage zone text-format file to define all the coverage zones for your ECDS network. Note The metric value of a default coverage zone is set to 20. If a particular SE is preferred for a user-defined coverage zone, the metric value in the Coverage Zone file should be set to a value less than 20. If a default coverage zone is preferred, then the metric value in the Coverage Zone file should be set to a value greater than 20. C-1

2 Zero-IP Based Configuration Appendix C Table C-1 defines the Coverage Zone file elements. Table C-1 Coverage Zone File Elements Tag Element Value Description location latitude float Not used in this release of ECDS longitude float Not used in this release of ECDS coveragezone network IP address Coverage zone IP address range. SE Service Engine name (string) Specifies the Service Engines serving the coverage zone specified in the network element. This can have one or more elements. metric integer Value indicating the proximity of the Service Engine to the end user. The lower the value, the closer the Service Engine is to the end user. location Value indicating the geographical coordinates (latitude and longitude) of the data center. CDNNetwork revision 1.0 Not used in this ECDS release. customername customer name Not used in this ECDS release. coveragezone This can have one or more coverage zones. Zero-IP Based Configuration The zero-ip based configuration is a catch-all condition for routing. It is a network entry in the Coverage Zone file defined as /0. It matches all client subnets. If the client subnet does not match any of the other network entries in the Coverage Zone file and a /0 network entry exists, then the SEs listed for that entry are considered for serving the client request. Following is an example of the zero-ip based configuration. <?xml version="1.0"?> <network> /32</network> <SE>U8-MDE1100-1</SE> <metric>5</metric> <network> /32</network> <SE>U8-MDE1100-2</SE> <metric>5</metric> <network> /0</network> <SE>U8-MDE1100-3</SE> <metric>20</metric> C-2

3 Appendix C Coverage Zone XML Schema Coverage Zone XML Schema The XML Schema file describes and dictates the content of the XML file. The coveragezone.xsd file contains the XML schema. The following code is the Coverage Zone XML schema: <?xml version="1.0" encoding="utf-8"?> <xsd:schema xmlns:xsd=" <xsd:annotation> <xsd:documentation> Revision: 1.0 </xsd:documentation> </xsd:annotation> <xsd:annotation> <xsd:documentation> Schema used to validate Cisco CDS CoverageZone file </xsd:documentation> </xsd:annotation> <xsd:simpletype name="ipaddresstype"> <xsd:union>    value="((1?[0-9]?[0-9] 2[0-4][0-9] 25[0-5])\.){3}(1?[0-9]?[0-9] 2[0-4][0-9] 25[0-5])/[0-9]+"/>             value="::/[0-9]+"/>  value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){7}/[0-9]+"/>    value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){5}::([a-fa-f0-9]{1,4})?/[0-9]+"/> C-3

4 Coverage Zone XML Schema Appendix C value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){4}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4})?)?/[0-9]+"/> value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){3}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,2})?/[0-9]+"/> value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){2}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,3})?/[0-9]+"/> value="[a-fa-f0-9]{1,4}:[a-fa-f0-9]{1,4}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,4})?/[0-9]+"/> value="[a-fa-f0-9]{1,4}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,4})?/[0-9]+"/>  value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){5}:(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[ 0-5]))/[0-9]+"/> value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){3}::([a-fa-f0-9]{1,4}:)?(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]) )\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9 ]) (2[0-4][0-9]) (25[0-5]))/[0-9]+"/> value="[a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){2}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4})?:)?(((1?[1-9])?[0-9]) (2[ 0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5] ))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))/[0-9]+"/> value="[a-fa-f0-9]{1,4}:[a-fa-f0-9]{1,4}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,2}:)?(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]) )\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))/[0-9]+"/> C-4

5 Appendix C Coverage Zone XML Schema value="[a-fa-f0-9]{1,4}::([a-fa-f0-9]{1,4}(:[a-fa-f0-9]{1,4}){0,2}:)?(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5 ]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))\.(((1?[1-9])?[0-9]) (2[0-4][0-9]) (25[0-5]))/[0-9]+"/> </xsd:union> <xsd:simpletype name="senametype"> <xsd:restriction base="xsd:string"> <xsd:minlength value="1"/> <xsd:maxlength value="80"/> <xsd:simpletype name="latitudetype"> <xsd:restriction base="xsd:float"> <xsd:mininclusive value="-90"/> <xsd:maxinclusive value="90"/> <xsd:simpletype name="longitudetype"> <xsd:restriction base="xsd:float"> <xsd:mininclusive value="-180"/> <xsd:maxinclusive value="180"/> <xsd:complextype name="locationtype"> <xsd:sequence> <xsd:element name="latitude" type="latitudetype"/> <xsd:element name="longitude" type="longitudetype"/> </xsd:sequence> </xsd:complextype> <xsd:complextype name="coveragezonetype"> <xsd:sequence> <xsd:element name="network" type="ipaddresstype" minoccurs="0"/> <xsd:element name="location" type="locationtype" minoccurs="0"/> <xsd:element name="se" type="senametype" minoccurs="1" maxoccurs="unbounded"/> <xsd:element name="metric" type="xsd:positiveinteger" minoccurs="1" maxoccurs="1"/> </xsd:sequence> </xsd:complextype> <xsd:element name="cdnnetwork"> <xsd:complextype> <xsd:sequence> <xsd:element name="revision" type="xsd:string" minoccurs="0" maxoccurs="1"/> <xsd:element name="customername" type="xsd:string" minoccurs="0" maxoccurs="1"/> <xsd:element name="coveragezone" type="coveragezonetype" minoccurs="0" maxoccurs="unbounded"/> </xsd:sequence> </xsd:complextype> </xsd:element> </xsd:schema> C-5

6 Coverage Zone File Examples Appendix C Coverage Zone File Examples The following sections show different Coverage Zone file scenarios: Scenario 1: Coverage Zone with Client Network Only, page C-6 Scenario 2: Coverage Zone with Geographical Location of the Datacenter Only, page C-6 Scenario 3: Coverage Zone with Client Network and Geographical Location of the Datacenter, page C-7 Scenario 4: Coverage Zone for Same Client Network with Different Weighted SEs, page C-8 Scenario 1: Coverage Zone with Client Network Only <?xml version= 1.0?>  <customername> Cisco Systems </customername>  <network> /16</network> <SE>MDE-1100-SE1</SE> <SE>MDE-1100-SE2</SE>  <network> /24</network> <SE>MDE-1100-SE3</SE> <SE>MDE-1100-SE4</SE>  <network> /24</network> <SE>MDE-1100-SE5</SE> <SE>MDE-1100-SE6</SE> Scenario 2: Coverage Zone with Geographical Location of the Datacenter Only <?xml version= 1.0?>  <customername> Cisco Systems </customername>  <location> <latitude>37</latitude> <longitude>-122</longitude> </location> <SE>MDE-1100-SE1</SE> <SE>MDE-1100-SE2</SE> C-6

7 Appendix C Coverage Zone File Examples  <location> <latitude>42</latitude> <longitude>-88</longitude> </location> <SE>MDE-1100-SE3</SE> <SE>MDE-1100-SE4</SE>  <location> <latitude>41</latitude> <longitude>-74</longitude> </location> <SE>MDE-1100-SE5</SE> <SE>MDE-1100-SE6</SE> Scenario 3: Coverage Zone with Client Network and Geographical Location of the Datacenter <?xml version= 1.0?>  <customername> Cisco </customername>  <network> /16</network> <SE>MDE-1100-SE1</SE> <SE>MDE-1100-SE2</SE>  <location> <latitude>41</latitude> <longitude>-74</longitude> </location> <SE>MDE-1100-SE3</SE> <SE>MDE-1100-SE4</SE>  <network> /24</network> <SE>MDE-1100-SE5</SE> <SE>MDE-1100-SE6</SE> C-7

8 Coverage Zone File Examples Appendix C Scenario 4: Coverage Zone for Same Client Network with Different Weighted SEs <?xml version="1.0"?>  <customername>cisco Systems</customerName> <network> /12 </network> <SE> dmz2-roam </SE> <metric> 10 </metric> <network> /12 </network> <SE> dmz2-is </SE> <metric> 20 </metric> C-8

Sticky and Proximity XML Schema Files

APPENDIX B Sticky and Proximity XML Schema Files This appendix describes how you can use the two XML schema files, included with the GSS, to describe and validate the sticky XML and proximity XML output