Forum Discussion
NimbostratusiControl REST API doesn't give any details for "show sys connection"
Dear Experts,
F5-BIG-IP (Trail version) - BIGIP-16.0.0-0.0.12-vmware
I am a newbie trying to explore more about F5-BIP-IP VE ( trail version) to adopt the same in our environment. "show sys connection" works perfect over the CLI but not over the REST API, Is it something restricted due to trail version?
Note: I do see all the supported links when i do the following..
curl -sk -u admin:admin https://10.81.1.212/mgmt/tm/ -H "Content-Type: application/json"
<snip>
{
"items": [
{
"link": "https://localhost/mgmt/tm/ltm/monitor/ftp"
},
{
"link": "https://localhost/mgmt/tm/analytics/apm-api-protection"
},
{
"link": "https://localhost/mgmt/tm/ltm/profile/smtp"
},
.....
......
<snip>
However when i try to get any information on the sub-modules i.e. /mgmt/tm/sys/connection , nothing works and i always see HTTP code 503 "Service is unavailable"
{
"code": 503,
"message": "Unable to process request /tm/sys/connection. Service is unavailable.",
"referer": "10.81.0.215",
"restOperationId": 15129470,
"kind": ":resterrorresponse"
}
Please help !
3 Replies
Have you tried the call locally (from the BIG-IP itself)? e.g.,
# curl -sku admin:admin https://localhost/mgmt/tm/sys/connection | jq . { "kind": "tm:sys:connection:connectionstats", "selfLink": "https://localhost/mgmt/tm/sys/connection?ver=14.1.2", "apiRawValues": { "apiAnonymous": "Sys::Connections\n" } }
Martin_CharlesHi, Yes the result is the same , even when i try it in the locally [root@F5-BIG-IP:Active:Standalone] config # curl -sku admin:admin https://localhost/mgmt/tm/sys/connection | jq { "code": 503, "message": "Unable to process request /tm/sys/connection. Service is unavailable.", "referer": "127.0.0.1", "restOperationId": 34615196, "kind": ":resterrorresponse" } Can you advise? -Martin
How about trying the equivalent action from:
1) tmsh: i.e., (from bash) 'tmsh show sys connection'. Use root.
2) Configuration Utility (BIG-IP's GUI). Use the same user (admin:xxxx).
If they both work but the iControl REST call did not work, try restarting the iControl REST processes: i.e., 'tmsh restart sys service restjavad'.
