IPLB is a feature which allows to distribute traffic toward internet or VPN between two or more IP resources. Two methods are allowed:
RR
: Round Robin. The packets are sequentially
sent through the IP resources of the group.
WQ
: Weighted Queue. The IP resource of the
group with the shorter transmission queue of the same priority is used
for the transmission of the packet under processing, otherwise packets
are sent sequentially on the resources of the group.
Use the command d iplb to display the IP load balancing table.
[12:24:12] ABILIS_CPX:d iplb
-------------------------------------------------------------------------------
ID: [DESCR:]
RULE: RES1:[..RES8:] GW1:[..GW8:]
-------------------------------------------------------------------------------
1 [test1]
WQ RES1:Ip-11 GW1:192.168.255.002
RES2:Ip-12 GW2:#
------------------------------------------------------------------------------
Meaning of the most important parameters:
Tip | |
---|---|
Interesting chapter: Section 83.22, “How to configure more VPN tunnels into IP Load Balancing (IPLB)”. |
This command allows to add an entry into the IPLB table.
[14:56:59] ABILIS_CPX:a iplb id:1 rule:wq descr:test res1:ip-1 res2:ip-2 gw1:192.168.0.232
COMMAND EXECUTED [14:57:06] ABILIS_CPX:d iplb
- Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------------- ------------------------------------------------------------------------------- ID: [DESCR:] RULE: RES1:[..RES8:] GW1:[..GW8:] ------------------------------------------------------------------------------- 1 [test] WQ RES1:Ip-1 GW1:192.168.000.232 RES2:Ip-2 GW2:# -------------------------------------------------------------------------------
Caution | |
---|---|
Changes made on the IP Load Balancing table are NOT immediately active, they can be activated by executing the initialization command init iplb. Then, remember to save the configuration (save conf). |
A routing which uses an IPLB indicates this condition by showing the IPLB in the “GW: or IPLB:” field of the D IPR output.
[15:20:35] ABILIS_CPX:d ipr
Destination routes and conditional source routes:
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|S| | | 129.132.002.021/32 | 255.255.255.255 | |D 2| 1|
|*|C| | | 192.168.000.201/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 3|120|
| |S| | | 192.168.001.000/24 | 255.255.255.000 | |D 4| 1|
|*|C| | | 192.168.031.000/24 | 255.255.255.000 | |D 21| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | (IPLB ID:01 UP) | 1| 1|
| |S| | | 000.000.000.000/0 | 000.000.000.000 | | 3|120|
| |C| | | | OUT-IP | |D 22| |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
Tip | |
---|---|
Interesting chapter: Section 83.22, “How to configure more VPN tunnels into IP Load Balancing (IPLB)”. |
This command allows to remove an entry of the IPLB table.
[15:19:33] ABILIS_CPX:d iplb
- Not Saved (SAVE CONF) ------------------------------------------------------- ------------------------------------------------------------------------------- ID: [DESCR:] RULE: RES1:[..RES8:] GW1:[..GW8:] ------------------------------------------------------------------------------- 1 [test1] WQ RES1:Ip-11 GW1:192.168.255.002 RES2:Ip-12 GW2:# ------------------------------------------------------------------------------ [15:20:21] ABILIS_CPX:c iplb id:1
COMMAND EXECUTED [15:20:33] ABILIS_CPX:d iplb
- Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------------- ------------------------------------------------------------------------------- ID: [DESCR:] RULE: RES1:[..RES8:] GW1:[..GW8:] ------------------------------------------------------------------------------- *** NO IPLB ENTRY DEFINED ***
Caution | |
---|---|
Changes made on the IP Load Balancing table are NOT immediately active, they can be activated by executing the initialization command init iplb. Remember to save the configuration (save conf). |
This command allows to change the parameters of an entry inside the IPLB table:
[15:26:20] ABILIS_CPX:d iplb
- Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------------- ------------------------------------------------------------------------------- ID: [DESCR:] RULE: RES1:[..RES8:] GW1:[..GW8:] ------------------------------------------------------------------------------- 1 [test] WQ RES1:Ip-1 GW1:192.168.000.232 RES2:Ip-2 GW2:# ------------------------------------------------------------------------------- [15:26:24] ABILIS_CPX:s iplb id:1 res2:ip-3
COMMAND EXECUTED [15:26:58] ABILIS_CPX:d iplb
- Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------------- ------------------------------------------------------------------------------- ID: [DESCR:] RULE: RES1:[..RES8:] GW1:[..GW8:] ------------------------------------------------------------------------------- 1 [test] WQ RES1:Ip-1 GW1:192.168.000.232 RES2:Ip-3 GW2:# -------------------------------------------------------------------------------
Caution | |
---|---|
Use command init iplb to activate changes on the IP Load Balancing. Then, remember to save the configuration (save conf). |