TASK 13.26:TCP Load Distribution with NAT <method of pool creation>

Is there any added benefit to creating the pool the way the SG does it?  

or is it just there to show us an alternate way ?

 

SG did it this way

ip nat pool LOAD_BALANCE prefix-length 24 type rotary

 address 155.1.0.1 155.1.0.1

 address 155.1.0.2 155.1.0.2

 address 155.1.0.3 155.1.0.3

 

 

 

I did it this way


ip nat pool LOAD_BALANCE 155.1.0.1 155.1.0.3 prefix-length 24 type rotary








Thankyou for any clarity provided.





Tox!

Comments

  • The only advantage I see to use SG solution is if you have servers that reside in different subnets. With the config you used you can only specify one range but with the SG solution you could specify multiple ranges.

    R1#sh run | be ip nat

    ip nat pool TST2 prefix-length 24 type rotary

     address 155.1.0.1 155.1.0.3

     address 155.1.1.1 155.1.1.3

     address 155.1.2.1 155.1.2.3

    ip nat pool TST 155.1.0.1 155.1.0.3 prefix-length 24 type rotary

     

    However for the task at hand that should not matter. But if you got a task that wanted you to use IPs from different subnets you now have an extra tool at hand.

  • The only advantage I see to use SG solution is if you have servers that reside in different subnets. 

    Thanks Daniel :)

     

    Tox!

Sign In or Register to comment.