Does F5 VE trail version 11.3 support device service cluster(DSC) feature?

Yes, I have seen that V10 do not support this kind of redundant service. But I can not find the release note of this V11.3. So I am not sure I can setup DSC on VE trail 11.3.

I setup like the following: 1. specifying the IP address for the config sync 2. Specifying the IP address for the connection mirroring 3. Establish the device trust. After setup the device trust, VE1 can see VE2 in the device list, and VE2 can also see VE1 in the device list. 4. Create a sync-failover device group. I selected Sync-Failover and also selected Network Failover. 5. From VE1, In Device Management -> Overview. I can see that VE2 is disconnected. From VE1's log: May 8 16:21:54 bigip1 notice mcpd[5347]: 0107143c:5: Connection to CMI peer 198.18.31.102 has been removed May 8 16:21:59 bigip1 notice mcpd[5347]: 01071431:5: Attempting to connect to CMI peer 198.18.31.102 port 6699 May 8 16:21:59 bigip1 notice mcpd[5347]: 01071432:5: CMI peer connection established to 198.18.31.102 port 6699 May 8 16:21:59 bigip1 notice mcpd[5347]: 0107143c:5: Connection to CMI peer 198.18.31.102 has been removed May 8 16:22:04 bigip1 notice mcpd[5347]: 01071431:5: Attempting to connect to CMI peer 198.18.31.102 port 6699 May 8 16:22:04 bigip1 notice mcpd[5347]: 01071432:5: CMI peer connection established to 198.18.31.102 port 6699 May 8 16:22:04 bigip1 notice mcpd[5347]: 0107143c:5: Connection to CMI peer 198.18.31.102 has been removed May 8 16:22:09 bigip1 notice mcpd[5347]: 01071431:5: Attempting to connect to CMI peer 198.18.31.102 port 6699 May 8 16:22:09 bigip1 notice mcpd[5347]: 01071432:5: CMI peer connection established to 198.18.31.102 port 6699 May 8 16:22:09 bigip1 notice mcpd[5347]: 0107143c:5: Connection to CMI peer 198.18.31.102 has been removed

The same kind of log we can see in VE2. From the above the log. I think the network connection is OK, as you can see the connection is established; but it removed by the peer right away. There is no route problem, because if I tried use telnet to the peer server port 22, it is OK.