03-31-2010 09:22 PM - edited 03-04-2019 08:00 AM
Hi,
Greetings
We are currently problems on a 7606 router with IOS Version 12.2 (18) SXF14 which is presenting an abnormal behavior in its routing characteristics of the problem are:
Have a Cluster 7609 this device present failure, this not perform routing correct to any static router. The log BRBOG3 device are the following:
BorderRouterBOG3#sh running-config | inc 199.175.44.28
ip route 199.175.44.28 255.255.255.255 190.102.199.41
BorderRouterBOG3#sh running-config | inc 199.175.44.37
ip route 199.175.44.37 255.255.255.255 190.102.199.41 name VPN_CYCLELOGIC
BorderRouterBOG3#sh ip route 199.175.44.28
Routing entry for 199.175.44.28/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 190.102.199.41
Route metric is 0, traffic share count is 1
BorderRouterBOG3#sh ip rou
BorderRouterBOG3#sh ip route 199.175.44.37
Routing entry for 199.175.44.37/32
Known via "static", distance 1, metric 0
Routing Descriptor Blocks:
* 190.102.199.41
Route metric is 0, traffic share count is 1
BorderRouterBOG3#sh ip cef 199.175.44.28
199.175.44.28/32, version 1554, epoch 0, cached adjacency 190.102.199.41
0 packets, 0 bytes
via 190.102.199.41, 0 dependencies, recursive
next hop 190.102.199.41, GigabitEthernet1/2.63 via 190.102.199.41/32 (Default)
valid cached adjacency
BorderRouterBOG3#sh ip cef 199.175.44.37
199.175.44.37/32, version 1556, epoch 0, cached adjacency 190.102.199.41
0 packets, 0 bytes
via 190.102.199.41, 0 dependencies, recursive
next hop 190.102.199.41, GigabitEthernet1/2.63 via 190.102.199.41/32 (Default)
valid cached adjacency
BorderRouterBOG3#sh ip inter bri
BorderRouterBOG3#sh ip inter brief | inc 1/2.63
GigabitEthernet1/2.63 190.102.199.43 YES NVRAM up up
As you can see the results in the routing table seem consistent, without a trace But when you have the following results:
BorderRouterBOG3#traceroute 199.175.44.28
Type escape sequence to abort.
Tracing the route to 199.175.44.28
1 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
2 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
3 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
4 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
5 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
6 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
7 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
8 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
9 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
10 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
11 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
12 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
13 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
14 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
15 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
16 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
17 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
18 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
19 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
20 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
21 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
22 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
23 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
24 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
25 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
26 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
27 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
28 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
29 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
30 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
BorderRouterBOG3#traceroute 199.175.44.37
Type escape sequence to abort.
Tracing the route to 199.175.44.37
1 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
2 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
3 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
4 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
5 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
6 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
7 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
8 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
9 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
10 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
11 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
12 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
13 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
14 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
15 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
16 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
17 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
18 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
19 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
20 10.13.2.6 [AS 13489] 0 msec 4 msec 0 msec
21 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
22 10.13.2.6 [AS 13489] 0 msec 0 msec 4 msec
23 10.13.2.6 [AS 13489] 0 msec 0 msec 0 msec
24 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
25 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
26 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
27 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
28 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
29 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
30 10.13.2.6 [AS 13489] 4 msec 0 msec 0 msec
The interface is responding traces is in the same device:
BorderRouterBOG3# sh ip inter brief | inc 10.13.2.6
GigabitEthernet1/2.60 10.13.2.6 YES NVRAM up up
Making a trace from BRBOG1 device drawn from the results are:
BorderRouter1#traceroute 199.175.44.28
Type escape sequence to abort.
Tracing the route to 199.175.44.28
1 10.11.4.10 0 msec 4 msec 0 msec
2 *
10.13.2.6 0 msec 0 msec
3 10.13.2.6 4 msec 4 msec 4 msec
4 10.13.2.6 0 msec * 0 msec
5 10.13.2.6 4 msec 0 msec *
6 10.13.2.6 0 msec 4 msec 0 msec
7 10.13.2.6 4 msec 0 msec 4 msec
8 10.13.2.6 0 msec 4 msec 4 msec
9 10.13.2.6 0 msec 4 msec 4 msec
10 10.13.2.6 0 msec 4 msec *
11 10.13.2.6 0 msec 4 msec 0 msec
12 10.13.2.6 0 msec 0 msec 4 msec
13 * 0 msec 0 msec
14 10.13.2.6 0 msec 4 msec 0 msec
15 10.13.2.6 4 msec * 0 msec
16 10.13.2.6 4 msec 0 msec 4 msec
17 10.13.2.6 0 msec 4 msec 0 msec
18 * 0 msec 4 msec
19 10.13.2.6 4 msec * 0 msec
20 10.13.2.6 4 msec 4 msec 4 msec
21 10.13.2.6 0 msec 8 msec *
22 10.13.2.6 0 msec 4 msec 0 msec
23 10.13.2.6 4 msec 4 msec 4 msec
24 10.13.2.6 8 msec * 4 msec
25 10.13.2.6 0 msec 0 msec 4 msec
26 10.13.2.6 28 msec 4 msec 0 msec
27 10.13.2.6 4 msec 0 msec 0 msec
28 10.13.2.6 0 msec 4 msec 4 msec
29 10.13.2.6 4 msec 0 msec 4 msec
30 10.13.2.6 4 msec 4 msec 4 msec
Note how the team will pass this package to BRBOG3 and stay there despite the static routes that tell the way forward.
I am enclosing the show tech-support team. Any comments or recomment on this subject please let me know
Sincerely,
PEDRO PABLO PACHECO
|
Support & Operation Engineer Colombia |e-mail: ppacheco@desca.com
Teléfono: +57 1 3766900 Ext. 67266| Teléfono directo: +57 1 3767266 | fax: +57 1 3766900| MSN IM: libreton3@hotmail.com | Celular: +57 3174378091
Carrera 7 No 71-52 Torre A Piso 11 Bogota D.C., Colombia
P Antes de imprimir este correo, pregúntese si es necesario hacerlo.
This message and any attachments are intended only for the use of the individual to whom they are addressed and it may contain information that is privileged or confidential. If you have received this communication by mistake, please notify us immediately by e-mail or telephone.
Este mensaje y cualquier anexo son exclusivamente para la persona a quien van dirigidos y pueden contener información privilegiada o confidencial. Si usted ha recibido esta comunicación por error, le agradecemos notificarlo de inmediato por esta misma vía o por teléfono.
04-01-2010 03:17 AM
Hello Pedro,
what happens if :
you do a
clear ip route 199.175.44.28
clear ip route 199.175.44.37
I tried to verify if any PBR rule is involved but no local policy in global configuration mode is applied.
and if you try to traceroute other host routes using the same IP next-hop like
190.102.199.66
what is the result?
Hope to help
Giuseppe
04-05-2010 07:14 AM
Hi Guiseppe,
Greetings,
Guiseppe thanks you very much for your update, Today my customer will give access to the devices for apply your recommendation in a next email I will inform to you the result.
Thanks,
PEDRO PABLO PACHECO
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide