Virtual System is not able to start when using Domain objects in security rules on R75.40VS in VSX mode

Support Center > Search Results > SecureKnowledge Details

Solution ID	sk93346
Product	VSX, Enterprise Appliances
Version	R75.40VS
OS	Gaia, Crossbeam XOS
Platform / Model	VSX-1, Intel/PC, 4000, 12000 VSX, 21000 VSX, Power-1, 2000, UTM-1, Crossbeam, IP2450, IP1280
Date Created	02-Jul-2013
Last Modified	03-Sep-2013

Symptoms

Output of 'vsx stat -v' command shows that number of 'active' Virtual Systems is less than number of 'configured', and shows 'Unknown' for the problematic Virtual System:

Virtual Systems [active / configured]: Less_then_Total / Total ID | Type & Name | Security Policy | Installed at | SIC Stat -----+-------------------------+-------------------+-----------------+--------- VSID | S Virtual_System_Name...| Unknown | Unknown | Unknown
Output of 'cpwd_admin list' command shows that the 'STAT' (state) of relevant daemons is 'T' (terminated).

Example:

APP CTX PID STAT #START START_TIME MON COMMAND FWK_WD 4 0 T 0 [19:06:12] 21/4/2013 N fwk_wd -i 1 CPD 4 0 T 0 [19:00:11] 21/4/2013 N cpd FWD 4 0 T 0 [19:06:13] 21/4/2013 N fwd CPHAMCSET 4 0 T 9 [19:06:25] 21/4/2013 N cphamcset
Starting the FWD daemon under debug in the context of problematic Virtual System shows:

[Expert@VSX_FW_HostName:0]# vsenv VSID_of_problematic_VS [Expert@VSX_FW_HostName:VSID_of_problematic_VS]# fwd -d [fwd PID ... CPPRODIS_init_error_logging_ex: initialized error logging for product 'FW1' application 'fwd'. Log file is not set. [FWD PID ... fw_get_connected_unix: failed to connect to /cp/fwk/sensor_vs_VSID: Connection refused [FWD PID ... fw_get_connected_unix: failed to connect to /cp/fwk/sensor_vs_VSID: Connection refused [FWD PID ... connect_to_fwk_sensor_simple: failed to create socket: Connection refused [FWD PID ... fw_get_connected_unix: failed to connect to /cp/fwk/sensor_vs_VSID: Connection refused [FWD PID ... connect_to_fwk_sensor_simple: failed to create socket: Connection refused [FWD PID ... connect_to_fwk_sensor: failed to connect

Cause

FWK process for the problematic Virtual System crashes when Domain Objects are used in security rules on R75.40VS in VSX mode.

Solution

Note: To view this solution you need to Sign In .