StifleR
2.10
2.10
  • Start Here - StifleR 2.10
  • Introduction
    • StifleR Overview
      • The StifleR Solution
      • Managing Microsoft Data Transfer Services
    • Technical Overview
      • 2Pint BranchCache Administrator Guide
    • Features Overview
      • Control
      • Monitor
      • Automate
      • Other Features
      • StifleR Feature Details
    • Release Notes
  • Proof of Concept
    • Objectives and Prerequisites
    • Configure Microsoft Peer-to-Peer Components
    • Install and Configure StifleR
    • Testing and Validation
    • StifleR POC Quick Checklist
  • Planning
    • StifleR Server Considerations
    • StifleR Client Considerations
    • Firewall Ports
    • Permissions
    • Antivirus Exclusions
    • Network Topology
    • StifleR Generic Concepts
      • Client Leader Roles
        • Red Leader
        • Blue Leader
        • Green Leader
        • Examples of Leader Selection
      • Templates
      • Beacons
  • Installation
    • Overview
    • Server
      • StifleR Server Installation
      • StifleR Dashboard Installation
      • StifleR Beacon Installation
    • Client
      • StifleR Client Installation
      • Post Installation Checks
  • Configuration
    • Configuration Files
      • StifleR Server Configuration File
        • Using the AppSettings Override File
      • StifleR Client Configuration File
      • StifleR Dashboard Configuration File
    • Configuring BranchCache on Windows Server
    • Configuring Delivery Optimization
    • Configuring LEDBAT on CM DPs
    • Configuring a Beacon Server
    • Configuring StifleR SQL History
    • StifleR Network Locations
      • Automatic linking of Location, Network Groups and Networks
      • Network Topology Automation
      • Location Fields
        • Network Group Fields
          • Network Fields
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Prerequisites
      • Using a Web Server Certificate
        • Requesting a Web Server Certificate
      • Using a Self-Signed Certificate
      • Preparing the StifleR Dashboard Web Site for SSL
      • Configuring StifleR to Use SSL
      • Finding the Certificate Thumbprint
    • StifleR Client Access Control Options
  • Operations
    • Dashboard
      • Overview & Navigation
        • Home Page
        • Traffic & Downloads
          • Transfers & Downloads
            • How to use query hosts search?
          • Running Sequences
          • Weekly Downloads Activity
          • History
        • Devices
          • Clients
            • Client Details
              • How to use an extended search?
          • Servers
          • StifleR Server
            • Templates Detail
        • Cache Management
        • System Resource Usage
        • Network Topology
          • Maps
          • Countries
          • Locations
            • Bandwidth Allocations and Locations
          • Network Groups
          • Networks
        • Reporting & Diagrams
    • Client Management & Remote Tools
      • Remote PowerShell Session
      • Remote Performance Counter
      • Remote WMI Browsing
      • Remote Event Log Viewer
      • Remote Netmon Session
    • Monitoring
      • StifleR server health
      • StifleR client health
      • BranchCache Testing and Monitoring
    • Maintenance tasks
    • Bandwidth Management and Allocation
      • Bandwidth Tuning Monitoring and Control
    • Backup and Recovery
      • Moving the StifleR Server Databases to a New Drive on the Same Server
    • Troubleshooting
      • StifleR Client Command Line Options
      • BranchCache across Subnets
    • StifleR WMI Provider
Powered by GitBook
On this page
  • Example scenario #1 - Campus style location
  • Example scenario #2 - Small location with few clients
  1. Planning
  2. StifleR Generic Concepts
  3. Client Leader Roles

Examples of Leader Selection

Example scenario #1 - Campus style location

No local servers

500 clients

Several ethernet as well as a single WiFi network

BL on each physical network

GL’s on physical network serving WiFi clients

As GL are also distributed clients, they will serve BL’s

Example scenario #2 - Small location with few clients

  • One physical subnet and one WiFi subnet - so Location has two Network Groups

  • WiFi is routed separately to ethernet – multi location

  • 50 clients

  • No BL’s

  • No Green Leader

  • Two separate Red Leaders downloading seperate

Scenarios

Two subnets in distributed mode with just bridged distributed mode

Two networks, four clients. Two Blue Leaders two client participating.

In this case, we have several machines in each subnet. We bridge the probe messages and the probe matches, and also cache some key data. We bridge the Red Leader info first.

Two subnets in distributed mode with just bridged distributed mode

Two networks, three clients. Two Blue Leaders. One client requesting.

In this case, we have several machines in each subnet. We bridge the probe messages and the probe matches, and also cache some key data. We bridge the Red Leader info first.

One client in each network (Green Leader)

In this scenario we have two (or more) clients in each network. One of them will get the Green Leader role, and the other connects using Hosted Cache mode. In this case one machine will be Hosted Cache server (Green leader) and the other client gets it from the GL. The GL machine itself will be in any mode (distributed, local, hosted cache).

  1. Single client on single network – Template/Location settings apply.

  2. Three clients on single network – MC disabled – Hosted cache mode.

  3. Multiple networks – few clients on each. Hosted Cache mode.

  4. Multiple networks

  5. Multiple clients in distributed mode. BL & GL on one machine.

  6. Few clients on other networks – used single BL & GL

  7. Multiple networks

  8. Multiple clients in distributed mode. BL & GL on one machine.

  9. A bit more than few clients on other networks – used BL on same subnet

  10. Multiple networks

  11. Multiple clients in distributed mode. BL & GL on one machine.

  12. Multiple clients in distributed mode. BL & GL on one machine.

Ideas:

  1. If over x clients we add more GLs?

Blue Leader requesting content logi flow

  • Allow selection of Green Leaders

  • Selected Green Leaders becomes Blue Leaders on distributed networks

  • If we have 2 wifi networks with small number of clients and one distributed in same network group, the Green Leader is on distributed network only

  • Multiple Green Leaders from Subnet

  • One BL per subnet

  • Should we plan for multiple?

  • BL stops forwarding requests after 50 clients on subnet

PreviousGreen LeaderNextTemplates

Last updated 1 year ago