Closed mnaumiuk closed 3 years ago
Just to clarify the expected behavior:
If keep-alive-interval
is set to disabled
in an ltm profile fastl4
object, set the AS3 keepAliveInterval
value to 0.
@jszczepanski correct! keepAliveInterval (integer) set the value to number of seconds between keep-alive probes. A value of 0 seconds disables the feature. ACC is indeed converting incorrectly
[2021-10-26T19:33:01.428Z] [INFO]: ACC METADATA {
recognized: {
'ltm profile fastl4 /Common/keep_allive_test': { 'app-service': 'none', 'keep-alive-interval': 'disabled' }
},
supported: {
'ltm profile fastl4 /Common/keep_allive_test': { 'app-service': 'none', 'keep-alive-interval': 'disabled' }
},
unSupported: {},
declarationInfo: {
classes: { L4_Profile: 1 },
maps: {
applications: [ '/Common/Shared' ],
objects: [ '/Common/Shared/keep_allive_test' ],
tenants: [ '/Common' ]
},
total: 1
}
}
After
{
"class": "ADC",
"schemaVersion": "3.30.0",
"id": "urn:uuid:4e5adae1-b6e8-4dec-a980-1d2bdbed5ca1",
"label": "Converted Declaration",
"remark": "Auto-generated by AS3 Config Converter",
"Common": {
"class": "Tenant",
"Shared": {
"class": "Application",
"template": "shared",
"keep_allive_test": {
"keepAliveInterval": "disabled", ------- Should be a (integer)
"class": "L4_Profile"
}
}
}
}
Merge branch 'develop' into CHARON-508-fastl4-keep-alive-interval
Merge branch 'CHARON-508-fastl4-keep-alive-interval' into 'develop'
Environment
Summary
For fastl4 profile with "keep-alive-interval disabled" validation error "['/tenant_3/application_3/fastL4.FW_3.profile/keepAliveInterval: should be integer']" is returned.
Steps To Reproduce
Steps to reproduce the behavior:
Convert following config:
Observe the following error message:
The default value for fastl4 profile "keep-alive-interval" is disabled. *The default value (disabled) is not present in the config from the beginning, but if this value is changed to a different value and changed back to 0/disabled, then "keep-alive-interval disabled" is present in the config.
Reproduced by modifying keep-alive-interval for fastl4 profile:
Additionally, it seems that this is specific to (at least) fastl4 profile, for example, the tcp profile cannot take value "disabled" but "0":
Expected Behavior
For fastl4 profile no error with "keep-alive-interval disabled"
Actual Behavior
/tenant_3/application_3/fastL4.FW_3.profile/keepAliveInterval: should be integer