Skip to main content

Get the intercluster LIFs

Contributors netapp-ranuk

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

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

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.

2. Get the intercluster LIFs

HTTP method Path

GET

/occm/api/replication/intercluster-lifs
curl example
curl --location --request GET '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>'
Input

Query parameters:

  • <WORKING_ENV_ID> (workingEnvironmentId)

  • <WORKING_ENV_ID> (peerWorkingEnvironmentId)

Output

The JSON output example includes the list of LIFs.

JSON output example
{
    "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
        }
    ]
}