We are currently running HSRP in our core with 2 devices within 1 HSRP Group which is fine.
We have an adjacent building where all hosts use this HSRP instance as their Gateway which works fine.
However we have an issue in that SRST is failing in remote building as when connectivity is lost to core(CUCM) the default gateway for all the hosts is unreachable.
The Core switch in the remote building(lets call this SW3) has SVIs configured but device is not part of HSRP group.
I can add this device to HSRP group but have concerns:-
I never want this device SW3 to be the active router for the whole campus which I can do with setting the priority level to be the lowest is this the best practise or should I look at interface tracking.
If I add in SW3 to HSRP group will it have any impact/outage on current setup.
Any other thoughts on doing this, driver is to get SRST operational if we lose connectivity between buildings.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...