I have a switch catalyst C3560 who have configured two static routes:
ip address 10.0.0.0 255.0.0.0 184.108.40.206
ip address 10.100.0.0 255.255.255.0 172.20.20.20
When I try to connect to the IP 10.100.0.221, the switch matches with the first route and it becomes in a asymetric routing because the packet is going back through a incorrect peer.... There is some option to fix it??? Maybe configuring a track in the route??? Somebody can leave me an example??
If you want specifically the traffic to 10.100.0.221 to go over 220.127.116.11 and not over 172.20.20.20 as it does right now then I suggest that you add a third default route saying
ip route 10.100.0.221 255.255.255.255 18.104.22.168
Otherwise, there is absolutely nothing you can do on the local 3560 to influence how the responses are routed back. Remember, a route to a specific destination is totally independent from the route back.
To be absolutely sure how and why the packets get to the remote host and how they get back, you first need to be very sure about the source and destination IP address of these packets, and then do a traceroute from the source IP toward the remote host to see what routers does the packet traverse in the direction from you to the remote host, and then you should use the remote host and tell it to traceroute the path back to you. After you have the list of routers through which the packet flow in the forward and return direction, you need to inspect the last router that is correct and after which the packets take a different path that you would expect.
The problem is the way is through various firewall who are dropping the ICMP packets, then the traceroute isn't a nice test....
I have the control of two of this FW, but there is one which is controlled by other people, then I can't open ICMP to test it... I know the source and destination IP but the problem is in the routes. I have one route who summarizes all subnets 10.X.X.X, this route is sending traffic through one gateway and the network 10.100.0.X /24 is through other different gateway. When arrive a packet with destination 10.100.0.X, the switch matches with the first route and it should match with the second... I have configured weight in the route, but is not working properly.
What is the "route weight" you are talking about? If you are talking about the administrative distance then this is not an appropriate tool for this purpose - the administrativ distance only defines which route is more trustworthy when two or more different sources (routing protocols, static configuration) try to insert the same route (i.e. the same address and netmask) into the routing table. In such a case, the route with the smaller administrative distance will win
However, in your case, the administrative distance does not apply. If you define a static host route toward the specific IP address, using a netmask of 255.255.255.255, this route will be placed at the top of the routing table because the routing table is searched starting the longest prefixes and moving down toward shorter prefixes. You are adding a new route to your routing table, therefore the administrative distance is not truly relevant because there is no competing route in the routing table.
I am not sure if this is understandable so please feel welcome to ask further.
Sorry!! Yes, is the administrative distance!! I understand you, but is not working properly. I will have to check all the equipment controlled by me. If all is correct, then I will call to the people who manage the other equipment and we will do some test to reach a solution.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.