This lab will focus on configuration of the following items:
L1-3 Networking
Physical Interface Settings
L2 Connectivity (VLAN, VXLAN, etc.)
L3 Connectivity (Self IPs, Routing, etc.)
We will specifically cover the items in BOLD above in the following
labs. It should be noted that many permutations of the Device Onboarding
process exist due to the nature of different organizations. This class is
designed to teach enough information so that you can then apply the
knowledge learned and help articulate and/or deliver a specific solution
for your environment.
The following table and diagram lists the L2-3 network information used to
configure connectivity for BIG-IP A:
This lab shows how to configure VLAN tags, but does not deploy tagged
interfaces. To use tagged interfaces the tagged attribute needs
to have the value true
Perform the following steps to configure the VLAN objects/resources:
Expand the Lab1.4-BasicNetworkConnectivity folder in the
Postman collection.
Click the Step1:CreateaVLAN request in the folder. Click
Body and examine the JSON request body; the values for
creating the Internal VLAN have already been populated.
Click the Send button to create the VLAN
Repeat Step 1, however, this time modify the JSON body to create the
External VLAN using the parameters shown in the table above. In order to do
so you can replace the following:
name: Internal –> External
tag: 10 –> 20
interfaces[]-->name: 1.1 –> 1.2
Click the Step2:GetVLANs request in the folder. Click the
Send button to GET the VLAN collection. Examine the response
to make sure both VLANs have been created.
Perform the following steps to configure the Self IP objects/resources:
Click the Step3:CreateInternalSelfIP request in the folder. Click
Body and examine the JSON body; the values for creating the
Self-Internal Self IP have already been populated.
Note
The JSON body sets the VLAN to /Common/External on purpose.
You will modify this value in the steps below. Please do not change the
value.
Click the Send button to create the Self IP.
Click the Step4:CreateExternalSelfIP request in the folder and
click Send
Click the Step5:GetSelf-InternalSelfIPAttributes request in the
folder and click the Send button. Examine the VLAN settings
of the Resource. As noted above the Self IP has been assigned to the wrong
VLAN (intentionally).
Note
Postman has the ability to check the responses for specific values
to verify if the result of a request is what it is expected to be. The
Test Results for this request will show a failure for the
[CheckValue]vlan==/Common/Internal value. This is intentional
and you should continue to the next section.
In order to modify an existing object via the REST API, the URI path has to
be changed. In the previous examples we used a POST to create Resources under
a Collection, therefore, the URI used was that of the Collection itself.
If you wish to update/modify a Resource you must refer to the Resource
directly.
For example, the Collection URI for Self IPs is /mgmt/tm/net/self.
The Resource URI for the Self-Internal Self IP is
/mgmt/tm/net/self/~Common~Self-Internal. Notice that the BIG-IP
partition and object name has been added to the Collection URI to for the
Resource URI.
On the open Step5:GetSelf-InternalSelfIPAttributes request
change the request method from GET to PATCH. The PATCH method
is used to modify the attributes of an existing Resource.
Copy (Ctrl+c) the entire JSON RESPONSE from the previous GET
request.
Paste (Ctrl+v) the text into JSON Request body:
Note
Be sure to highlight any existing text and replace it while
pasting.
In the JSON body change the vlan attribute to /Common/Internal
and click Send:
Click the Step6:GetSelfIPs item in the collection. Click the
Send button to GET the Self IP collection. Examine the response to
make sure both Self IPs have been created and associated with the
appropriate vlan.
Perform the following steps to configure the Route object/resource:
Before creating the route, we double check the content of the routing table.
Click the Step7:GetRoutes item in the collection. Click the
Send button to GET the routes collection. Examine the response to
make sure there is no route.
Click the Step8:CreateaRoute item in the collection. Click
Body and examine the JSON body; the values for creating the
default route have already been populated.
Click the Send button to create the route.
Click the Step9:GetRoutes item in the collection again. Click the
Send button to GET the routes collection. Examine the response to
make sure the route has been created.
Task 5 – [Service Provider] Route Domain and Partition¶
In this task we will perform basic Route Domain and Partition configuration.
Perform following steps to complete this task:
Expand the Lab1.4A-RouteDomain&Partition in the Postman Collection
Send the requests in Steps 1-10 and verify the expected result occured on
BIG-IP A. For requests using the GET method you can review the response
JSON body rather than using the BIG-IP GUI.
Send the requests in Steps 11-18 to clean up the previously created Route
Domain, VLANS and Partitions
All route domain and partitions should now be deleted. Please confirm this on
BIG-IP A. Any configuration that remains from this task will interfere with
cluster setup in the subsequent labs.
