Symptoms
A configuration that contains custom 'SIP' or 'FirePass' monitors that is upgraded from a version earlier than v13.1.0 may either fail to load, or may result in a configuration that loads the first time after the upgrade, but cannot be re-loaded from the text config files.
If the BIG-IP system has partitions other than 'Common', the initial configuration load may fail with an error such as:
01070726:3: monitor /Common/sip-monitor in partition Common cannot reference SSL profile monitor parameter /Common/sip-monitor 1 SSL_PROFILE_NAME= in partition name-of-other-partition
If the BIG-IP system only has a 'Common' partition, the initial configuration load will succeed, but subsequent attempts to load the configuration (e.g., 'tmsh load sys config') may fail with this error:
Syntax Error:(/config/bigip.conf at line: 63) "user-defined" unknown property
Which corresponds to a SIP or FirePass monitor in the configuration such as:
ltm monitor sip /Common/test_sip_monitor {
cipherlist DEFAULT:+SHA:+3DES:+kEDH
compatibility enabled
debug no
defaults-from /Common/sip
destination *:*
filter 488
interval 5
mode tcp
time-until-up 0
timeout 16
user-defined SSL_PROFILE_NAME /Common/test_sip_monitor_ssl_profile
}
Impact
After upgrade, the configuration fails to load with an error such as:
01070726:3: monitor /Common/sip-monitor in partition /Common cannot reference SSL profile monitor parameter /Common/sip-monitor 1 SSL_PROFILE_NAME= in partition name-of-other-partition.
Alternatively, the configuration loads after upgrade, but the config file is corrupted, and will fail to load (such as after a system restart, or upon explicit 'tmsh load sys config'), with an error such as:
Syntax Error:(/config/bigip.conf at line: 63) "user-defined" unknown property
Conditions
Custom 'SIP' or 'FirePass' monitor is configured, and the config is upgraded from a version earlier than v13.1.0 to version v13.1.0.
Workaround
Remove custom 'SIP' and 'FirePass' monitors from the configuration, and re-create them manually after upgrade is complete.
Fix Information
In this release, a configuration that contains a custom 'SIP' or 'FirePass ' monitor from a version earlier than v13.1.0 now loads correctly and continues to load as expected.
