Get the intercluster LIFs

07/10/2024 Contributors

You can use this workflow to retrieve the intercluster LIFs used in a cluster peering relationship.

This workflow varies slightly depending on the cloud provider you are using.

Step 1. Select the working environment

Based on the cloud provider, you need to perform the corresponding workflow to retrieve the identifier of the working environment.

AWS

Perform the workflow Get AWS working environments and choose the publicId values for the working environment query parameters.

Azure

Perform the workflow Get Azure working environments and choose the publicId values for the working environment query parameters.

Google cloud

Perform the workflow Get Google Cloud working environments and choose the publicId values for the working environment query parameters.

Step 2. Get the intercluster LIFs

You can issue the REST API call to get the intercluster LIFs.

HTTP method and endpoint

This REST API call uses the following method and endpoint.

HTTP method	Path
GET	/occm/api/replication/intercluster-lifs

Curl example

curl --request GET \
--location "https://cloudmanager.cloud.netapp.com/occm/api/replication/interclusterlifs?workingEnvironmentId=<WORKING_ENV_ID>&peerWorkingEnvironmentId=<WORKING_ENV_ID>" \
--header "Content-Type: application/json" \
--header "x-agent-id: <AGENT_ID>" \
--header "Authorization: Bearer <ACCESS_TOKEN>"

Additional input parameters

The JSON input example includes the minimum list of parameters.

Query parameters:

<WORKING_ENV_ID> (workingEnvironmentId)
<WORKING_ENV_ID> (peerWorkingEnvironmentId)

JSON Output example

The JSON output example includes the list of LIFs.

Example output

{
    "interClusterLifs": [
        {
            "name": "intercluster",
            "address": "10.138.0.154",
            "netmaskLength": 32,
            "port": "e0a",
            "node": "zivgcp01we03-01",
            "status": "up",
            "isPeered": true
        }
    ],
    "peerInterClusterLifs": [
        {
            "name": "intercluster",
            "address": "10.138.0.147",
            "netmaskLength": 32,
            "port": "e0a",
            "node": "zivgcp01we02-01",
            "status": "up",
            "isPeered": true
        }
    ]
}