> On Nov 15, 2016, at 1:50 PM, Eero Volotinen <[email protected]> wrote: > > same ports? you mean that same port assigment and nic can be different type? > > eero
No. Hardware should be as identical as possible. 100% identical is best. If LAN is em0 on one side, it must be em0 on the other. > > 15.11.2016 11.36 ip. "Steve Yates" <[email protected]> kirjoitti: > >> Any hardware should work fine. They recommend a separate NIC/port >> for the sync traffic since if syncing states there can be a lot of traffic >> (if not syncing state there is probably very little). I don't think it >> needs to be identical hardware but the rules would need to copy over so it >> would need the same ports. >> >> One gotcha that caught me...under "System/High Availability >> Sync/Configuration Synchronization Settings (XMLRPC Sync)" there is a >> "Remote System Username" field. That field is ignored, and "admin" is >> always used. >> >> -- >> >> Steve Yates >> ITS, Inc. >> >> -----Original Message----- >> From: List [mailto:[email protected]] On Behalf Of Eero >> Volotinen >> Sent: Tuesday, November 15, 2016 2:20 PM >> To: pfSense Support and Discussion Mailing List <[email protected]> >> Subject: [pfSense] pfsense + carp + ha >> >> Hi List, >> >> What are requirements for pfsense ha clustering? does any of x86 hardware >> work with ha? does hardware need to be identical? >> >> _______________________________________________ >> pfSense mailing list >> https://lists.pfsense.org/mailman/listinfo/list >> Support the project with Gold! https://pfsense.org/gold >> > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
