Network fault tolerance for LAN clientsLAN to LAN over internet*nix CARP or VMWare Fault Tolerance?How to...

15% tax on $7.5k earnings. Is that right?

Has the laser at Magurele, Romania reached a tenth of the Sun's power?

How could a planet have erratic days?

Why should universal income be universal?

Why do some congregations only make noise at certain occasions of Haman?

Will number of steps recorded on FitBit/any fitness tracker add up distance in PokemonGo?

Does the Linux kernel need a file system to run?

How to make money from a browser who sees 5 seconds into the future of any web page?

Doesn't the system of the Supreme Court oppose justice?

Pre-mixing cryogenic fuels and using only one fuel tank

How much theory knowledge is actually used while playing?

What kind of floor tile is this?

How can I write humor as character trait?

Does Doodling or Improvising on the Piano Have Any Benefits?

What to do when eye contact makes your coworker uncomfortable?

Giving feedback to someone without sounding prejudiced

Make a Bowl of Alphabet Soup

Creating two special characters

Is this part of the description of the Archfey warlock's Misty Escape feature redundant?

Does "he squandered his car on drink" sound natural?

It grows, but water kills it

US tourist/student visa

A variation to the phrase "hanging over my shoulders"

How to preserve electronics (computers, iPads and phones) for hundreds of years



Network fault tolerance for LAN clients


LAN to LAN over internet*nix CARP or VMWare Fault Tolerance?How to detect weak points in my lanNeed help diagnosing network performance issuesWhat Are VMware ESXi/vSphere Fault Tolerance Bandwidth RequirementsHow to implement a network fault tolerance on a Windows Server 2008 R2, Single Server - Dual NIC? Only Windows Services like DNS, DHCP, File ServerExtend wireless LAN with several access points?Ethernet Router, switch and network routesHow to configure two firewalls for two WANs and one LANConfiguring a switch with WAN and LAN













0















Goal: Provide fault tolerance for LAN clients so access to a service with a service-level agreement (SLA) is not interrupted in the event of an incident with a physical switch.



Question: Is there a configuration which would provide fault tolerance for LAN clients over Ethernet via a single wall port per client?



Stop reading here if the answer to my first question is yes.



--



With Ethernet, In the following topology if the switch stops working the client no longer has access to services provided over the LAN.



client<--> wall port <--> patch panel <--> switch



With Wi-Fi, In the following topology if a single switch stops working the client continues to have access to services provided over the LAN, if the client is in range of both access points (AP) 01 and 02.



                        Wi-Fi client
/
Cluster A Wi-Fi AP 01 Cluster A Wi-Fi AP 02
|| ||
ethernet ethernet
/
switch A switch B


I'm unaware if there is a standard for Wi-Fi clustering. The type I am referring to is present in Linksys LAPAC line of Wi-Fi access points.



While two NICs and two wall ports for each client would overcome this limitation, it is unrealistic in a usual office environment.



In this scenario would it be preferential to use Wi-Fi with clustering? If so, am I correct in assuming that it would it imply that Wi-Fi with clustering delivers better uptime (especially with mobile devices)?



From a best practices perspective how would this configuration be considered?



Thank you for your answers and input.









share







New contributor




Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    Goal: Provide fault tolerance for LAN clients so access to a service with a service-level agreement (SLA) is not interrupted in the event of an incident with a physical switch.



    Question: Is there a configuration which would provide fault tolerance for LAN clients over Ethernet via a single wall port per client?



    Stop reading here if the answer to my first question is yes.



    --



    With Ethernet, In the following topology if the switch stops working the client no longer has access to services provided over the LAN.



    client<--> wall port <--> patch panel <--> switch



    With Wi-Fi, In the following topology if a single switch stops working the client continues to have access to services provided over the LAN, if the client is in range of both access points (AP) 01 and 02.



                            Wi-Fi client
    /
    Cluster A Wi-Fi AP 01 Cluster A Wi-Fi AP 02
    || ||
    ethernet ethernet
    /
    switch A switch B


    I'm unaware if there is a standard for Wi-Fi clustering. The type I am referring to is present in Linksys LAPAC line of Wi-Fi access points.



    While two NICs and two wall ports for each client would overcome this limitation, it is unrealistic in a usual office environment.



    In this scenario would it be preferential to use Wi-Fi with clustering? If so, am I correct in assuming that it would it imply that Wi-Fi with clustering delivers better uptime (especially with mobile devices)?



    From a best practices perspective how would this configuration be considered?



    Thank you for your answers and input.









    share







    New contributor




    Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      Goal: Provide fault tolerance for LAN clients so access to a service with a service-level agreement (SLA) is not interrupted in the event of an incident with a physical switch.



      Question: Is there a configuration which would provide fault tolerance for LAN clients over Ethernet via a single wall port per client?



      Stop reading here if the answer to my first question is yes.



      --



      With Ethernet, In the following topology if the switch stops working the client no longer has access to services provided over the LAN.



      client<--> wall port <--> patch panel <--> switch



      With Wi-Fi, In the following topology if a single switch stops working the client continues to have access to services provided over the LAN, if the client is in range of both access points (AP) 01 and 02.



                              Wi-Fi client
      /
      Cluster A Wi-Fi AP 01 Cluster A Wi-Fi AP 02
      || ||
      ethernet ethernet
      /
      switch A switch B


      I'm unaware if there is a standard for Wi-Fi clustering. The type I am referring to is present in Linksys LAPAC line of Wi-Fi access points.



      While two NICs and two wall ports for each client would overcome this limitation, it is unrealistic in a usual office environment.



      In this scenario would it be preferential to use Wi-Fi with clustering? If so, am I correct in assuming that it would it imply that Wi-Fi with clustering delivers better uptime (especially with mobile devices)?



      From a best practices perspective how would this configuration be considered?



      Thank you for your answers and input.









      share







      New contributor




      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      Goal: Provide fault tolerance for LAN clients so access to a service with a service-level agreement (SLA) is not interrupted in the event of an incident with a physical switch.



      Question: Is there a configuration which would provide fault tolerance for LAN clients over Ethernet via a single wall port per client?



      Stop reading here if the answer to my first question is yes.



      --



      With Ethernet, In the following topology if the switch stops working the client no longer has access to services provided over the LAN.



      client<--> wall port <--> patch panel <--> switch



      With Wi-Fi, In the following topology if a single switch stops working the client continues to have access to services provided over the LAN, if the client is in range of both access points (AP) 01 and 02.



                              Wi-Fi client
      /
      Cluster A Wi-Fi AP 01 Cluster A Wi-Fi AP 02
      || ||
      ethernet ethernet
      /
      switch A switch B


      I'm unaware if there is a standard for Wi-Fi clustering. The type I am referring to is present in Linksys LAPAC line of Wi-Fi access points.



      While two NICs and two wall ports for each client would overcome this limitation, it is unrealistic in a usual office environment.



      In this scenario would it be preferential to use Wi-Fi with clustering? If so, am I correct in assuming that it would it imply that Wi-Fi with clustering delivers better uptime (especially with mobile devices)?



      From a best practices perspective how would this configuration be considered?



      Thank you for your answers and input.







      switch local-area-network fault-tolerance





      share







      New contributor




      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 7 mins ago









      Jack.LJack.L

      11




      11




      New contributor




      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Jack.L is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "2"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Jack.L is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f959452%2fnetwork-fault-tolerance-for-lan-clients%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Jack.L is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Jack.L is a new contributor. Be nice, and check out our Code of Conduct.













          Jack.L is a new contributor. Be nice, and check out our Code of Conduct.












          Jack.L is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f959452%2fnetwork-fault-tolerance-for-lan-clients%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

          Список ссавців Італії Природоохоронні статуси | Список |...

          Українські прізвища Зміст Історичні відомості |...