Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 322
  • Last Modified:

Tracking interface for Policy route

Hi ,

Pls have a llok at my scenario and below are the brief about the topology.

R1 : L3 Switch and IP routing enabled

Aswitch : L2 switch

VLAN 13PC : it is a PC connected to 13 vlan in R1 core switch

VLAN40PC2 : connected to L2 switch in 40th VLAN


VLAN40PC2 default gateway is 192.168.40.1 , which is 40th vlan ip in Core-Switch(in R1)

VLAN13PC default gateway is 192.168.13.1, which is 13th vlan ip in Core-Switch(in R1)


R1(Core-Sw) and Aswitch both are connected and it is TRUNK Link


Communication between VLAN40PC2 and VLAN13PC is happening  over Trunk link..


My requirement :

When the connectivity (trunk link) between R1(core-Sw) and Aswitch(L2) fails ,

VLAN13PC should be reachable over R1-> R7 -> R8 -> Aswitch to VLAN40PC2



To Resolve the  above requirement , i have done the following configurations :



1. In R1 (Core-Sw) , i have configured Policy Route for Source VLAN13PC to destination
VLAN40PC2 with set next hop as R7 f0/0 IP address

2.In R8 Router, i have configuerd SUB interfaces with 40th VLAN and 3 vlan


Result after configured above :

It is pinging from   VLAN40PC2 and VLAN13PC  using Policy route

But After Trunk link connectivity (trunk link) between R1(core-Sw) and Aswitch(L2) restored,
It is still using policy route only


My question is ,

Can we track Trunk interface (connectivity  between R1(core-Sw) and Aswitch(L2)) and can we apply trunk interface to a VLAN 13.

So that when trunk link failes , 13 vlan pc automatically communicates to 40th vlan PC
                                               and
when trunk link gets up with out any other configuration  it has to communicate over trunk link..
Elsec-VLAN40.png
0
RAMU CH
Asked:
RAMU CH
  • 6
  • 6
1 Solution
 
RAMU CHAuthor Commented:
Thanks for the info..

But the attachement is not helpful to my scenario..

I have L3 switch and does it supports tracking to a trunk interface.?

Pls see the topology once again  and check my requirement..

Regards
Ram
0
 
Don JohnstonInstructorCommented:
Without knowing what the platform and IOS version is, there is no way to answer the question of whether your switch supports object tracking.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
RAMU CHAuthor Commented:
Cisco IOS Software, 3700 Software (C3725-ADVENTERPRISEK9-M), Version 12.4(15)T5, RELEASE SOFTWARE (fc4)


Pls provide information : How to track a L2 trunk link

As per your attched link, we can track L3 interface using IPSLA and i need,  how to track
L2 trunk link

My requirement is

If Trunk link failes , traffic should go over Router and once Trunk link gets up , the traffic
should go via trunk link


Regards
Ramu
0
 
Don JohnstonInstructorCommented:
R1 : L3 Switch and IP routing enabled
Cisco IOS Software, 3700 Software (C3725-ADVENTERPRISEK9-M), Version 12.4(15)T5, RELEASE SOFTWARE (fc4)

Just to be clear, your version info appears to indicate that R1 is a 3725 Router.  

Is R1 a router or a switch?
0
 
RAMU CHAuthor Commented:
IT is in GNS3 LAB called RouterSwitch

We are using L3 switch
0
 
Don JohnstonInstructorCommented:
It doesn't matter if the interface being tracked is layer2, layer3, a trunk, etc.  An interface is an interface. It doesn't matter what the interface is doing.

But for basic routing, there is no need to track an interface since if the interface state is down, the route is removed from the routing table.

If you're using a routing protocol, that will handle the failover. If you're not using a routing protocol, create floating static routes with the R7-R8-Aswitch path having a higher administrative distance.

If you're locked in to doing PBR, create a static route using the R7-R8-Aswitch path, then a failure of the outbound interface would result in the traffic using the static route.
0
 
RAMU CHAuthor Commented:
I would like t o inform you that Aswitch is a L2 switch not L3 switch then how can we do float static routing over core-Sw
0
 
RAMU CHAuthor Commented:
I have followed your attached Link of Multiple interface tracking and i would like to know

what is the difference between rtr and IP SLA


I have configured IP SLA on a cisco 3750 , L3 switch but when i do applying , it is accepting


RemoteRTR(config)#track 1 ip  sla
% Invalid input detected at '^' marker.

But i can apply rtr to track ID

so What is the difference of IP SLA and RTR


Regards
Ramu
0
 
Don JohnstonInstructorCommented:
It's the same thing.  At some point (around 12.3 or 12.4), Cisco changed the commands from "rtr" to "ip sla".
0
 
RAMU CHAuthor Commented:
Tks
0
 
Don JohnstonInstructorCommented:
How was my answer lacking?
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now