| Step 1 |
Gather the necessary information from the Azure site that you could use for your Cisco Cloud APIC endpoint selector.
| Note
|
These steps assume that you are configuring the instance in Azure first, then adding an endpoint selector for Cisco Cloud APIC afterward; however, you can also add an endpoint selector in Cisco Cloud APIC first, then perform this Azure instance configuration step afterward, at the end of these endpoint selector procedures.
|
|
| Step 2 |
Log into the Cisco Nexus Dashboard Orchestrator, if you aren't already logged in.
|
| Step 3 |
In the left pane, click Schemas, then select the schema that you created earlier.
|
| Step 4 |
Determine how you want to create the endpoint selector.
-
If you want to create an endpoint selector that could be applied to any additional cloud site in the future, follow these
procedures:
-
In the left pane, leave the template selected.
Do not select a specific site for these procedures.
-
In the middle pane, select the EPG that you created for the cloud site.
-
In the right pane, in the CLOUD PROPERITES area, click + next to SELECTORS to configure the endpoint selector.
-
In the Add New End Point Selector dialog, enter a name in the END POINT SELECTOR NAME field, based on the classification that you use for this endpoint selector.
-
Click + Expression, then select the type of endpoint selector.
For an endpoint selector created this way, the only option available under the Key field is EPG.
-
Go to Step 5.
-
If you want to create an endpoint selector specifically for this cloud site, follow these procedures:
-
In the left pane, select the cloud site.
-
In the middle pane, select the EPG that you created for the cloud site.
-
In the right pane, in the SITE LOCAL PROPERITES area, under the SELECTORS area, click + next to SELECTOR to configure the endpoint selector.
-
In the Add New End Point Selector dialog, enter a name in the END POINT SELECTOR NAME field, based on the classification that you use for this endpoint selector.
For example, for an endpoint selector with the IP Subnet classification, you might use a name such as IP-Subnet-EPSelector.
-
Click + Expression, then select the key that you want to use for the endpoint selector.
-
IP Address: Used to select by the IP address or subnet. The value for an IP address as an endpoint selector should fall under the user
subnet created under the CIDR in Adding Sites to the Schema.
In addition, specifically for Azure scale set VMs, the value for an IP address as an endpoint selector must be a complete
subnet that was configured in Adding Sites to the Schema where that scale set resides. It cannot be an IP address within the subnet.
For example, if you used the following values in these fields for Azure scale set VMs:
-
CIDR: 10.1.0.0/16
-
Subnet: 10.1.0.0/24
Then a valid value for an IP address as an endpoint selector would be 10.1.0.0/24. Entries of 10.1.0.1/32 or 10.1.0.0/16 would not be valid values for an IP address as an endpoint for Azure scale set VMs.
| Note
|
IPv6 is not supported for Cisco Cloud APIC in Azure. You must use a valid IPv4 address for this field.
|
-
Region: Used to select by the Azure region of the endpoint.
-
If you want to create a custom tag for the endpoint selector, start typing in the Type to search or create field to enter the custom tag or label, then click Create on the new field to create a new custom tab or label.
Using the example earlier in these procedures when you were adding a tag in Azure, you might create the custom tag Location in this field, to match the Location tag that you added in Azure earlier.
|
| Step 5 |
In the Operator field, choose the operator that you want to use for the endpoint selector.
The options are:
-
Equals: Used when you have a single value in the Value field.
-
Not Equals: Used when you have a single value in the Value field.
-
In: Used when you have multiple comma-separated values in the Value field.
-
Not In: Used when you have multiple comma-separated values in the Value field.
-
Has Key: Used if the expression contains only a key.
-
Does Not Have Key: Used if the expression contains only a key.
|
| Step 6 |
In the Value field, choose which value that you want to use for the endpoint selector, based on the choices that you made for the two
previous fields. You can have multiple comma-separated entries in the Value field, where a logical OR exists between the entries in this field.
| Note
|
The Value field is not displayed if Has Key or Key Not Exist is selected for the Operator field.
|
For example, if you want to have a specific Azure region for the endpoint selector, such as westus, you might make the following selections in this screen:
-
Key: Region
-
Operator: Equals
-
Value: westus
As another example, assume that you used the following values in these fields:
The EPG rules will be applied to all endpoints with an IP address in this situation.
As a final example, assume that you used the following values in these fields:
In this situation, the EPG rules will be applied to all endpoints with the Azure tag key Location, regardless of the location
value.
|
| Step 7 |
Click the checkmark when you have finished creating this endpoint selector expression.
|
| Step 8 |
Determine if you want to create additional endpoint selector expressions.
If you create more than one expression under a single endpoint selector, a logical AND exists between those expressions. For
example, assume you created two sets of expressions under a single endpoint selector:
-
Endpoint selector 1, expression 1:
-
Key: Region
-
Operator: Equals
-
Value: eastus
-
Endpoint selector 1, expression 2:
-
Key: IP
-
Operator: Equals
-
Value: 192.0.2.1/24
In this case, if both of these expressions are true (if the region is eastus AND if the IP address belongs to subnet 192.0.2.1/24), then that endpoint
will be assigned to the Cloud EPG.
Click the checkmark after every additional expression that you want to create under this endpoint selector.
|
| Step 9 |
When you have finished creating the expressions for this endpoint selector, click SAVE in the lower right corner of the Add New End Point Selector.
If you create more than one endpoint selector under an EPG, a logical OR exists between those endpoint selectors. For example,
assume you had created endpoint selector 1 as described in the previous step, and then you created a second endpoint selector
as described below:
In this case:
Then that end point is assigned to the Cloud EPG.
|
| Step 10 |
When you have finished creating the endpoint selectors, click SAVE in the upper right corner.
|
| Step 11 |
Click on the DEPLOY TO SITES button at the top right corner of the screen to deploy the schema to the sites.
You should see a message saying Successfully Deployed at this point.
|
Feedback