Yes you have to do it.
Le 2018-01-15 à 09:31, luca comes a écrit :
> Thanks Fabrice,
> after the change on the master node the port is correctly
> listening. Node 2 and 3 are still not listen on port 443, should I do
> it on every node?
>
> Luca
>
>
> ------------------------------------------------------------------------
> *Da:* Fabrice Durand <[email protected]>
> *Inviato:* lunedì 15 gennaio 2018 15:10
> *A:* luca comes; Fabrice Durand via PacketFence-users
> *Oggetto:* Re: R: [PacketFence-users] no httpd portal in a Cluster
>
>
> Hello Luca,
>
> try that:
>
>
> [CLUSTER]
> management_ip=172.27.17.7
>
> [CLUSTER interface ens160]
> ip=172.27.17.7
> type=management
>
> [CLUSTER interface ens192.2445]
> ip=10.255.20.7
> type=internal
>
> [CLUSTER interface ens192.2446]
> ip=10.255.30.7
> type=internal
>
> [pfnac01]
> management_ip=172.27.17.5
>
> [pfnac02]
> management_ip=172.27.17.6
>
> [pfnac03]
> management_ip=172.27.17.3
>
> [pfnac01 interface ens160]
> ip=172.27.17.5
> type=management,portal
> mask=255.255.255.0
>
> [pfnac02 interface ens160]
> ip=172.27.17.6
> type=management,portal
> mask=255.255.255.0
>
> [pfnac03 interface ens160]
> ip=172.27.17.3
> type=management,portal
> mask=255.255.255.0
>
>
> [pfnac01 interface ens192.2445]
> enforcement=vlan
> ip=10.255.20.5
> type=internal
> mask=255.255.255.0
>
> [pfnac02 interface ens192.2445]
> enforcement=vlan
> ip=10.255.20.6
> type=internal
> mask=255.255.255.0
>
> [pfnac03 interface ens192.2445]
> enforcement=vlan
> ip=10.255.20.10
> type=internal
> mask=255.255.255.0
>
>
> [pfnac01 interface ens192.2446]
> enforcement=vlan
> ip=10.255.30.5
> type=internal
> mask=255.255.255.0
>
>
> [pfnac02 interface ens192.2446]
> enforcement=vlan
> ip=10.255.30.6
> type=internal
> mask=255.255.255.0
>
> [pfnac03 interface ens192.2446]
> enforcement=vlan
> ip=10.255.30.10
> type=internal
> mask=255.255.255.0
>
>
> and do a pfcmd configreload hard and restart packetfence.
>
>
> Regards
>
> Fabrice
>
>
>
> Le 2018-01-15 à 08:54, luca comes a écrit :
>> Hi Fabrice,
>> underneath my cluster.conf, as you can see I also tried to put the
>> high availability flag on the management without success:
>>
>> # Cluster configuration file for active/active
>> # This file will have it deactivated by default
>> # To activate the active/active mode, set a management IP in the
>> cluster section
>> # Before doing any changes to this file, read the documentation
>> [CLUSTER]
>> management_ip=172.27.17.7
>>
>> [CLUSTER interface ens160]
>> ip=172.27.17.7
>> type=management,high-availability
>>
>> [CLUSTER interface ens192.2445]
>> ip=10.255.20.7
>> type=internal
>>
>> [CLUSTER interface ens192.2446]
>> ip=10.255.30.7
>> type=internal
>>
>> [pfnac01]
>> management_ip=172.27.17.5
>>
>> [pfnac01 interface ens160]
>> ip=172.27.17.5
>> type=management,high-availability
>> mask=255.255.255.0
>>
>> [pfnac01 interface ens192.2445]
>> enforcement=vlan
>> ip=10.255.20.5
>> type=internal
>> mask=255.255.255.0
>>
>> [pfnac01 interface ens192.2446]
>> enforcement=vlan
>> ip=10.255.30.5
>> type=internal
>> mask=255.255.255.0
>>
>> [pfnac02]
>> management_ip=172.27.17.6
>>
>> [pfnac02 interface ens160]
>> ip=172.27.17.6
>> type=management,high-availability
>> mask=255.255.255.0
>>
>> [pfnac02 interface ens192.2445]
>> enforcement=vlan
>> ip=10.255.20.6
>> type=internal
>> mask=255.255.255.0
>>
>> [pfnac02 interface ens192.2446]
>> enforcement=vlan
>> ip=10.255.30.6
>> type=internal
>> mask=255.255.255.0
>>
>> [pfnac03]
>> management_ip=172.27.17.3
>>
>> [pfnac03 interface ens160]
>> ip=172.27.17.3
>> type=management,high-availability
>> mask=255.255.255.0
>>
>> [pfnac03 interface ens192.2445]
>> enforcement=vlan
>> ip=10.255.20.10
>> type=internal
>> mask=255.255.255.0
>>
>> [pfnac03 interface ens192.2446]
>> enforcement=vlan
>> ip=10.255.30.10
>> type=internal
>> mask=255.255.255.0
>>
>>
>> Luca
>> ------------------------------------------------------------------------
>> *Da:* Fabrice Durand via PacketFence-users
>> <[email protected]>
>> <mailto:[email protected]>
>> *Inviato:* lunedì 15 gennaio 2018 14:37
>> *A:* [email protected]
>> <mailto:[email protected]>
>> *Cc:* Fabrice Durand
>> *Oggetto:* Re: [PacketFence-users] no httpd portal in a Cluster
>>
>>
>> Hello Lucas,
>>
>> can i have the cluster.conf file ?
>>
>> Regards
>>
>> Fabrice
>>
>>
>>
>> Le 2018-01-15 à 05:10, luca comes via PacketFence-users a écrit :
>>>
>>> Hi all,
>>>
>>> I've successfully migrated a single node infrastructure to a full 3
>>> node cluster, all things has gone well but I have only one problem.
>>> After the cluster configuration the https port is not listening
>>> neither on the virtual IP nor the local IPs of each server on the
>>> management interface. This is needed for my sponsor guest
>>> authentication, I checked httpd.portal and is correctly started on
>>> each server, also on each management interface the portal listing
>>> daemons is added to the configuration. What I'm missing? Please help
>>> me otherwise I cannot put it in production.
>>>
>>>
>>> Thanks
>>>
>>>
>>> Luca
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>>
>>> _______________________________________________
>>> PacketFence-users mailing list
>>> [email protected]
>>> <mailto:[email protected]>
>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>
>> --
>> Fabrice Durand
>> [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x135) ::
>> www.inverse.ca <http://www.inverse.ca>
>> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
>> (http://packetfence.org)
>
> --
> Fabrice Durand
> [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x135) ::
> www.inverse.ca <http://www.inverse.ca>
> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
> (http://packetfence.org)
--
Fabrice Durand
[email protected] :: +1.514.447.4918 (x135) :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence
(http://packetfence.org)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
