Member not found via REST call

[Inder]

Hi guys,

I am getting an unexpected error where below REST call is not returning me the member detail. The error says - Object not found, when I can clearly locate the partition-member combination through the F5 web interface.

REST call: https://F5Host.com/mgmt/tm/ltm/pool/~partition~pool/members/~partition~member

Output:

{

 "code": 404,

 "message": "Object not found - /partition/member:443",

 "errorStack": [],

 "apiError": 1

}

Any suggestions?

[Dario_Garrido]

Hello.

This is the correct syntax

/mgmt/tm/ltm/pool/<pool name>/members/~<partition>~<node name>:<port>/

REF - https://support.f5.com/csp/article/K13225405#poolmember

In your case, try to use the port and also complete the word members using 's' at the end.

"Object not found - /partition/member:443",

KR,

Dario.

[Inder]

Hello Dario, thanks for your response but even this syntax is not fetching me the result. I am getting result only for the Common partition but not for the client specific partition. Refer the attached screenshots.

Result for Common partition: OK

Result for client specific partition (Dario's Syntax): 404 Not Found

Result for client specific partition: 404 Not Found

[Dario_Garrido]

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.