Referring to the attachment, therehas two Uplink. one is BTCL and another is Mango. They have two IP pool, one is 22.214.171.124/24 which is published through Mango and another is 126.96.36.199/24 which is published through BTCL. Thus incoming BGP load balance has been ensured.
but problem is that two link have the unequal bandwidth and
Customer don’t want to import full routing table rather it just import default route only.
Their requirement was that, traffic comes from 188.8.131.52/24 only should go through MANGO link.
That’s why I have created one traffic policy named MANGO (see attachment name PBR_first_solution.txt). in that way customer initial requirement was served.
But at this point customer facing one problem like below(see the topology.ppt)
When PC(184.108.40.206) try to communicate with mail server(220.127.116.11)
It can communicate no problem, but traffic is going to mango link and then come back to mail server. Customer told that, this should not be happened. They asked me to give them a solution and without changing the redirect ip-nexthop command.
To handle this situation I have created one more traffic classifier and behavior(PBR_final solution) which has the common name bb
in “classifier bb” where I mentioned about ACL 3777. which is below
acl number 3777
rule 5 permit ip source 18.104.22.168. 24 destination 22.214.171.124. 24
rule 10 permit ip source 126.96.36.199. 24 destination 188.8.131.52. 24
Along with the classifier bb I have created one traffic behavior “bb” where I permit ACL 3777 traffic such that NE40E can check the local routing table that is If source traffic is from 184.108.40.206 network and destination is local network that means either 220.127.116.11/24 network or 18.104.22.168/24 network , NE40E will check the local routing table and it will not go to Mango Link.
I have declare the new classifier and behavior bb like the below sequence.
traffic policy mango
classifier bb behavior bb
classifier aa behavior aa
ip address 22.214.171.124 255.255.255.0
traffic policy mango inbound
so when PC(126.96.36.199) try to communicate with mail server(188.8.131.52) at first traffic come to gi 1/0/0 interface where traffic policy Mango is applied to inbound. Then based on traffic policy Mango , first it will check whether the destination address is belongs to its local network or not with “classifier bb behavior bb”. if it is in local routes it send back the traffic through gi1/0/0 interface and reach to local destination like mail server(184.108.40.206) through its local backbone.
If PC(220.127.116.11) try to communicate with remote network like 18.104.22.168 server first it will check “classifier bb behavior bb” and find that destination network is not local then it checks “classifier aa behavior aa” which redirect all traffics to Mango link through “redirect ip-nexthop 22.214.171.124 “command.
Thus customer requirement is full filled and customer is satisfied with my solution
Actually I use “ redirect ip-nexthop 126.96.36.199” command to redirect the outgoing traffic towards Mango link from the source 188.8.131.52/24 network.
But in our router when we use redirect command it does not check its local routing table at all, it just forward all traffic to 184.108.40.206 until that interface is physically down.
So in this case when PC(220.127.116.11) tried to communicate with mail server(18.104.22.168) all traffic from PC comes to interface gi1/0/0 ,it just send all traffic to mango link without checking whether the destination is its local network or remote.
in summary our router has so many features and we can use those features to solve any problem using our skill wisely.