<commit_before>{{{
  "title": "Dedicated Load Balancer Basic Management",
  "date": "12-15-2014",
  "author": "<NAME>",
  "attachments": [],
  "contentIsHTML": true
}}}

<h3>Description&nbsp;</h3>
<p>This KB will go over the basics of creating a Load Balancer VIP and Service Group when using dedicated Load Balancers</p>
<h3>Prerequisites</h3>
<ul>
  <li>Must have a dedicated Netscaler available in your environment</li>
  <li>Must have an Admin login to your netscaler</li>
  <li>Must have Java installed and configured correctly. See KB: <a href="../General/how-to-configure-java-settings-to-access-web-user-interfaces.md"> How-to-Configure-Java</a>
      <br />
    </a>
  </li>
  <li>Understand the basic architecture of how a Netscaler works. See KB:<a href="/load-balancing-dedicated-vs-shared">Load Balancing Dedicated vs Shared</a>
      <br />
    </a>
  </li>
</ul>
<h3>Notes</h3>
<ul>
  <li>Traffic destined to the Load Balancer will hit the <strong>Virtual Server(VIP)</strong> first. From there it will determine which <strong>member</strong> of the attached <strong>Service Group</strong> to send traffic too based on the <strong>Load Balancing Method.</strong>
  </li>
</ul>
<h3>Detailed Steps</h3>
<ol>
  <li>Log into the Netscaler web interface using http://netscalerManagementip with an Admin account</li>
</ol>
<h3>Create Service Group</h3>
<ol>
  <li>Expand the menu Load Balancing, select Service Groups, and click Add. (Version 10.1 and later this is within Traffic Management)</li>
  <ul>
    <li>Description of each required field</li>
    <ul>
      <li>Service Group Name: The name we reference when attaching the Service Group to the VIP</li>
      <li>Protocol: This should match the type of traffic that will be used between the Load Balancer and the members of the Service Group. Note: If you are doing SSL offloading, then the Service Group type will be HTTP while the VIP type is SSL. (Since
        traffic between the Load Balancer and members will not be re-encrypted.)</li>
      <li>Members: Specify the IP and port that should be used for each member of the Load Balanced pool. You can add additional optional parameters if necessary</li><commit_msg>fix link<commit_after>{{{
  "title": "Dedicated Load Balancer Basic Management",
  "date": "12-15-2014",
  "author": "<NAME>",
  "attachments": [],
  "contentIsHTML": true
}}}

<h3>Description&nbsp;</h3>
<p>This KB will go over the basics of creating a Load Balancer VIP and Service Group when using dedicated Load Balancers</p>
<h3>Prerequisites</h3>
<ul>
  <li>Must have a dedicated Netscaler available in your environment</li>
  <li>Must have an Admin login to your netscaler</li>
  <li>Must have Java installed and configured correctly. See KB: <a href="../General/how-to-configure-java-settings-to-access-web-user-interfaces.md"> How-to-Configure-Java</a>
      <br />
    </a>
  </li>
  <li>Understand the basic architecture of how a Netscaler works. See KB:<a href="./load-balancing-dedicated-vs-shared.md">Load Balancing Dedicated vs Shared</a>
      <br />
    </a>
  </li>
</ul>
<h3>Notes</h3>
<ul>
  <li>Traffic destined to the Load Balancer will hit the <strong>Virtual Server(VIP)</strong> first. From there it will determine which <strong>member</strong> of the attached <strong>Service Group</strong> to send traffic too based on the <strong>Load Balancing Method.</strong>
  </li>
</ul>
<h3>Detailed Steps</h3>
<ol>
  <li>Log into the Netscaler web interface using http://netscalerManagementip with an Admin account</li>
</ol>
<h3>Create Service Group</h3>
<ol>
  <li>Expand the menu Load Balancing, select Service Groups, and click Add. (Version 10.1 and later this is within Traffic Management)</li>
  <ul>
    <li>Description of each required field</li>
    <ul>
      <li>Service Group Name: The name we reference when attaching the Service Group to the VIP</li>
      <li>Protocol: This should match the type of traffic that will be used between the Load Balancer and the members of the Service Group. Note: If you are doing SSL offloading, then the Service Group type will be HTTP while the VIP type is SSL. (Since
        traffic between the Load Balancer and members will not be re-encrypted.)</li>
      <li>Members: Specify the IP and port that should be used for each member of the Load Balanced pool. You can add additional optional parameters if necessary</li>
{'fraction_non_alphanumeric': 0.11326786937656999, 'fraction_numerical': 0.00959123087462891, 'mean_word_length': 4.081206496519721, 'pattern_counts': {'":': 10, '<': 123, '<?xml version=': 0, '>': 123, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '409751', 'n_tokens_mistral': 1354, 'n_tokens_neox': 1305, 'n_words': 544}