WSM management tunnel

rv@kaufmann.dkrv@kaufmann.dk
in Firebox - Management Software

WSM management server 12.6.4

I have setup a SSL management tunnel between a T15 and WSM server behind a M370 cluster. The management tunnel is up and running, but management does not work as the provided management networks by DVCP are wrong.

Currently the T15 gets assigned 172.16.1.0/24, which is a fysical interface on the M370 and 173.31.255./24 which does not exist at all.

My management server is on vlan subnet 172.16.252.0/24 and this is also the server the T15 tries to reach, but is not allowed by the automatic created DVCP-Allow-SSLVPN-Mgmt-Clients policy - which has 172.16.1.0/24 and 172.31.255.0/24 configured.

2021-03-01 17:07:59 dvcpcd **Error: Unable to connect to server 172.16.252.10 - connection timed out Debug

Why do WSM server assign wrong management networks via DVCP configuration to the M370 device?

Regards
Robert

Comments

  • rv@kaufmann.dkrv@kaufmann.dk

    I had to include the public ip address also in the management part on the T15 device - i only had the internal configured.

    And reading another document it´s expected with the above subnets. All my mistake.

    /Robert

Sign In to comment.