Member not found via REST call

Hello Inder.

The message is "object not found" because maybe you have some mistake when you write the name of your object in the URL.

The best way to troubleshoot this is following the json branches from the root (list of pools).

# curl -sku admin:xxxx -X GET https://localhost/mgmt/tm/ltm/pool/ | json-format | grep -e \"link\"
        "link": "https://localhost/mgmt/tm/ltm/pool/~APPLICATIONS~mypool/members?ver\u003d12.1.4.1",
		
# curl -sku admin:xxxx -X GET https://localhost/mgmt/tm/ltm/pool/~APPLICATIONS~mypool/members | json-format | grep -e \"selfLink\" 
  "selfLink": "https://localhost/mgmt/tm/ltm/pool/~APPLICATIONS~mypool/members?ver\u003d12.1.4.1",
      "selfLink": "https://localhost/mgmt/tm/ltm/pool/~APPLICATIONS~mypool/members/~APPLICATIONS~2.2.2.2:80?ver\u003d12.1.4.1",
 
# curl -sku admin:xxxx -X GET https://localhost/mgmt/tm/ltm/pool/~APPLICATIONS~mypool/members/~APPLICATIONS~2.2.2.2:80 | json-format 
{
  "kind": "tm:ltm:pool:members:membersstate",
  "name": "2.2.2.2:80",
  "partition": "APPLICATIONS",
  "fullPath": "/APPLICATIONS/2.2.2.2:80",
  ...
}

If you cannot find the pool in its partition in the fisrt query, then you should validate that your user has access to this partition (RBAC).

KR,

Dario.