iControl REST Cookbook - Virtual Server (ltm virtual)

This cookbook lists selected ready-to-use iControl REST curl commands for virtual-server related resources. Each recipe consists of the curl command, it's tmsh equivalent, and sample output. In thi...
Updated Oct 30, 2024
Version 3.0
devops
iControlREST
TMSH
Arie's avatar
Arie
Icon for Altostratus rankAltostratus
Sep 05, 2019

The section about disabling VIPs seems to be incorrect.

curl -sku admin:admin  https://<host>/mgmt/tm/ltm/<vs> \
  -X PATCH -H "Content-Type: application/json" \
  -d '{"enabled": false}' \

Results in HTTP 400 Bad Request.

{
    "code": 400,
    "message": "one or more properties must be specified",
    "errorStack": [],
    "apiError": 26214401
}

Changing the JSON to the following does the trick:

{
    "disabled": true
}

Subsequently, the JSON response is:

{
    "kind": "tm:ltm:virtual:virtualstate",
    "name": "TestVIP",
    [...]
    "disabled": true,
    [...]
}

For comparison, an enabled VIP looks like this:

{
    "kind": "tm:ltm:virtual:virtualstate",
    "name": "TestVIP",
    [...]
    "enabled": true,
    [...]
}

Version: 12.1.2

  • chin_ntt's avatar
    chin_ntt
    Icon for Nimbostratus rankNimbostratus
    Oct 31, 2024

    Why is the value true without quotes?

    "disabled": true

    "enabled": true

    Shouldn't the value in JSON data be inside double quotes? 

    • JRahm's avatar
      JRahm
      Icon for Admin rankAdmin
      Oct 31, 2024

      some fields are ints or booleans, not strings

      • chin_ntt's avatar
        chin_ntt
        Icon for Nimbostratus rankNimbostratus
        Oct 31, 2024

        Thanks for the clarification JRahm.

        I thought the word true was being parsed as a string. But as you mentioned, it's considered as a Boolean.

        I see IP addresses are inside double quotes. So I guess those are considered as strings and not integers!