Forum Discussion
Hi Kazeem, It is possible to do bind over multiple SMPP backend server and keep them open. This is the concept of MBLB in the previous TMOS version or MRF in the newer TMOS version. However, it is better to do it one by one instead of opening bind all the same time. The iRule above written by Nat (natty76) should do the trick. Try that first and see what the road block.
Hello Joko, Thanks for the heads up, the smpp binds hit the 1st smpp firewall, when the request is to be forwarded to the second F5 ip, it returns an invalid system id field.
How can a system id be included inside an SMPP VIP
My topology involves an ESME, two smpp firewalls which communicate via separate F5 vip's To the SMSC.
So, my topology looks like this.
ESME>>>1ST F5 VIP
1ST F5 VIP forwards t0 1st smpp firewalls.
1st smpp firewalls are configured to forward to second f5 VIP.
1ST SMPP FW>>>>>2ND F5 VIP
2nd F5 VIP load balances to 2nd smpp firewalls.
2nd f5 vip>>>2nd smpp firewalls.
2nd smpp firewalls are configured to forward to third f5 vip.
2nd smpp firewalls >>>>> third f5 vip.
third f5 vip load balances to SMSC.
3rd f5 vip>>>SMSC.
The irule used is listed in comment. The bind tranceiver message hits the 1st smpp firewall, and fails on hitting the second F5 VIP, as the second F5 VIP doesn't have the SYSTEM ID parameter configured.
How do i configure the system ID on the 2nd and third F5 VIP's.