load Archives - Page 4 of 4 - Simon Technology Blog

Configuration and non-equivalent load balancing experiments of EIGRP protocol

eigrp protocol: From the perspective of packet encapsulation, EIGRP is encapsulated in the IP header. The protocol is a three-layer protocol and is a CISCO private protocol that supports load balan

September 30, 2021By Simo Load Balance balance, configuration, EIGRP, experiment, load, non-equivalent, protocolLeave a Comment

EIGRP non-equivalent load balancing, connecting an article.

Network Diagram As follows:
IP address configuration:
R1 13.1.1.1 12.1.1.1 11.1.1.1 (PC1 is 11.1.1.2 used to test connectivity)
R2 12.1.1.2 24.1.1.2
R3 13.1.1.3 34.1.1.3
R4 24.1.1.4 34.1.1.4 4

September 30, 2021By Simo Load Balance article, balance, connection, EIGRP, load, non-equivalent, oneLeave a Comment

WCF service behind the F5 load balancer (WSHTTPBINDING binding)

Current settings:
– I have a wsHttpBding WCF service, please refer to the service configuration below
– I have implemented ServiceHostFactory to solve the incorrect pattern location and soap add

September 30, 2021By Simo Load Balance back, binding, Equalizer, F5, load, service, WCF, WSHTTPBINDINGLeave a Comment

ASP.NET – Session Status of Network Load Balancing Scheme

We currently set up the current server for the website:

>Server 1: Management System & Database
>Server 2: Public Site
>Server 3: Public site

Use Windows network load balancing system

September 29, 2021By Simo Asp ASP, ASP.NET, balance, load, network, program, session, stateLeave a Comment

[Reptile] Load version of the producer and consumer model

”’
Lock version Producer and consumer model
”’
import threading
import random
import time
gMoney < /span>= 1000 # Original amount
gLoad = threading.Lock()
gTime = 0 # production times
class Prod

September 28, 2021By Simo Web Crawler Consumers, Edition, load, mode, Producer, reptileLeave a Comment

Start-BIOS loaded into the RAM?

I know that at startup, B IOS loads the first sector (512 bytes) of the predefined device driver on memory 0x7c00, and then jumps to that address. < p>

So, the memory from 0x7c00 to 0x7dff is