[es] - cisco load sharing/balansing

markom
Marko Milivojević
Network Engineer
Google
Mountain View

Član broj: 18427
Poruke: 4227
213.176.148.*

Sajt: https://markom.rs

+16 Profil

Re: cisco load sharing/balansing

^{10.06.2007. u 22:28 - pre 205 meseci}

Odlazni saobraćaj možeš da "balansiraš" sa dve statičke rute ka dva različita udaljena rutera:

Code:
R2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     192.0.1.0/30 is subnetted, 2 subnets
C       192.0.1.0 is directly connected, Serial1/0
C       192.0.1.4 is directly connected, Serial1/1
R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#ip route 0.0.0.0 0.0.0.0 192.0.1.2
R2(config)#ip route 0.0.0.0 0.0.0.0 192.0.1.6
R2(config)#do sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.0.1.6 to network 0.0.0.0

     192.0.1.0/30 is subnetted, 2 subnets
C       192.0.1.0 is directly connected, Serial1/0
C       192.0.1.4 is directly connected, Serial1/1
S*   0.0.0.0/0 [1/0] via 192.0.1.6
               [1/0] via 192.0.1.2

Obrati pažnju na poslednje dve linije. U zavisnosti od toga kako je podešen ruter, radiće ili per-packet (loše ako radiš NAT, a i inače) ili per-destination load sharing. Obrati pažnju da per-destination neće rezultirati u 50:50 raspodeli saobraćaja.

Takođe, ukoliko su linkovi različite "veličine", možeš imati problema sa ovim rešenjem.

Drugo, znatno bolje rešenje je da se dogovoriš sa provajderom za multilink PPP na te dve veze.

Što se NAT-a tiče - šta tačno želiš da postigneš?

OV SM
LA PK

Odgovor na temu

THE_NELE
bih

Član broj: 7359
Poruke: 20
*.sa-ob.bih.net.ba.

Profil

Re: cisco load sharing/balansing

^{15.06.2007. u 15:56 - pre 205 meseci}

E fala za ovo!
Sto se tice NATa ono jel moguce postici da mi oba public interfejsa ucestvuju u NAT-u. Stavio sam na oba interfejsa
ip nat outside al NAT mi prevodi IP adrese u adresu samo jednog interfejsa, tj. samo sam mogao jedan od ova dva interfejsa ukljuciti u NAT proces:
ip nat inside source list 1 interface Serial0/0/1 overload
Unapried zahvalan!

Nele

Odgovor na temu

markom
Marko Milivojević
Network Engineer
Google
Mountain View

Član broj: 18427
Poruke: 4227
*.du.xdsl.is.

Sajt: https://markom.rs

+16 Profil

Re: cisco load sharing/balansing

^{15.06.2007. u 17:32 - pre 205 meseci}

Mislim da za to moraš da imaš pool, tj. provajder treba da ti rutira određeni adresni prostor.

Recimo da imaš situaciju sa slike.

Neka je R2 provajderov ruter, a R1 tvoj. Ispod je primer koji bi trebalo da radi. Uključio sam i statičku translaciju za sam ruter i "servere" koji su možda tamo negde.

R1:

Code:
interface FastEthernet0/0
ip address 192.168.1.1 255.255.255.0
ip nat inside
!
interface Serial1/0
ip address 150.12.1.1 255.255.255.252
ip nat outside
!
interface Serial1/1
ip address 150.12.2.1 255.255.255.252
ip nat outside
!
ip local pool Internet 150.168.1.4 150.168.1.15
ip route 0.0.0.0 0.0.0.0 150.12.1.2 name Default_1
ip route 0.0.0.0 0.0.0.0 150.12.2.2 name Default_2
ip nat inside source list 1 pool Internet overload
ip nat inside source static 192.168.1.1 150.168.1.1
ip nat inside source static 192.168.1.2 150.168.1.2
access-list 1 deny 192.168.1.0 0.0.0.15
access-list 1 permit 192.168.1.0 0.0.0.255

R2:

Code:
interface Serial1/0
ip address 150.12.1.2 255.255.255.252
ip verify unicast source reachable-via rx
!
interface Serial1/1
ip address 150.12.2.2 255.255.255.252
ip verify unicast source reachable-via rx
!
ip route 150.168.1.0 255.255.255.240 150.12.1.1 name Route_1
ip route 150.168.1.0 255.255.255.240 150.12.2.1 name Route_2

Code:
R1#sh ip route | b Gatew
Gateway of last resort is 150.12.2.2 to network 0.0.0.0

C    192.168.1.0/24 is directly connected, FastEthernet0/0
     150.12.0.0/30 is subnetted, 2 subnets
C       150.12.2.0 is directly connected, Serial1/1
C       150.12.1.0 is directly connected, Serial1/0
S*   0.0.0.0/0 [1/0] via 150.12.2.2
               [1/0] via 150.12.1.2
R1#sh ip nat translations verbose
Pro Inside global      Inside local       Outside local      Outside global
--- 150.168.1.1        192.168.1.1        ---                ---
    create 00:06:19, use 00:06:19 timeout:0,
    flags:
static, use_count: 0, entry-id: 3, lc_entries: 0
--- 150.168.1.2        192.168.1.2        ---                ---
    create 00:06:15, use 00:06:15 timeout:0,
    flags:
static, use_count: 0, entry-id: 4, lc_entries: 0

Code:
Gateway of last resort is not set

     150.12.0.0/30 is subnetted, 2 subnets
C       150.12.2.0 is directly connected, Serial1/1
C       150.12.1.0 is directly connected, Serial1/0
     150.168.0.0/28 is subnetted, 1 subnets
S       150.168.1.0 [1/0] via 150.12.2.1
                    [1/0] via 150.12.1.1
R2#debug ip packet
IP packet debugging is on
R2#ping 192.168.1.1 repeat 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
.
Success rate is 0 percent (0/1)
*Mar  1 00:44:20.803: IP: s=150.12.1.2 (local), d=192.168.1.1, len 100, unroutable
R2#ping 150.168.1.1 repeat 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 150.168.1.1, timeout is 2 seconds:
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 140/140/140 ms
*Mar  1 00:44:49.095: IP: tableid=0, s=150.12.1.2 (local), d=150.168.1.1 (Serial1/0), routed via FIB
*Mar  1 00:44:49.099: IP: s=150.12.1.2 (local), d=150.168.1.1 (Serial1/0), len 100, sending
*Mar  1 00:44:49.231: IP: tableid=0, s=150.168.1.1 (Serial1/0), d=150.12.1.2 (Serial1/0), routed via RIB
*Mar  1 00:44:49.235: IP: s=150.168.1.1 (Serial1/0), d=150.12.1.2 (Serial1/0), len 100, rcvd 3

OV SM
LA PK

Prikačeni fajlovi

NAT.png - 15.1k

Odgovor na temu

markom
Marko Milivojević
Network Engineer
Google
Mountain View

Član broj: 18427
Poruke: 4227
*.du.xdsl.is.

Sajt: https://markom.rs

+16 Profil

Re: cisco load sharing/balansing

^{15.06.2007. u 18:00 - pre 205 meseci}

Evo možda malo bolje ilustracije:

R2:

Code:
interface Loopback1
ip address 150.3.3.3 255.255.255.255
!

Code:
R2#ping 150.168.1.1 repeat 1 source loopback 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 150.168.1.1, timeout is 2 seconds:
Packet sent with a source address of 150.3.3.3
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 76/76/76 ms

/* paket ide ka R1 */
*Mar  1 00:03:28.179: IP: tableid=0, s=150.3.3.3 (local), d=150.168.1.1 (Serial1/0), routed via FIB
*Mar  1 00:03:28.183: IP: s=150.3.3.3 (local), d=150.168.1.1 (Serial1/0), len 100, sending

/* odgovor stiže od R1 */
*Mar  1 00:03:28.251: IP: tableid=0, s=150.168.1.1 (Serial1/1), d=150.3.3.3 (Loopback1), routed via RIB
*Mar  1 00:03:28.255: IP: s=150.168.1.1 (Serial1/1), d=150.3.3.3, len 100, rcvd4

Obradi pažnju da je R2 poslao paket preko Serial1/0, a primio odgovor nazad preko Serial1/1

OV SM
LA PK

Odgovor na temu