We have two L3 3750 switches running HSRP and routing for various Vlans on our corporate network. Rapid PVST is running across our entire WAN. We are introducing a third party solution for remote communications over MPLS. When interconnecting this equipment to our core network, we have experienced less than desirable failover times of 32 seconds and recovery times of 60 seconds. The vendors engineers are telling is that the interoperability between IEEE spanning tree and Rapid PVST is the culprit. They are suggesting two scenarios - either converting our corporate network to MST (which I prefer not to do but provides us the fastest fail/recovery times) or adjust the timers on our Rapid PVST forwarding timer to 4 seconds. What would the implications be to change these timers on our network, and if I choose to do this, do I only do it at the core (on the two devices that would become root bridge)? I have been doing some reading that says to not mess with the timers, but nowhere do I see reasons why. Can anyone shed some light on this for me?
What protocol are running between your 3750 switches and the MPLS provider? You can simply use a couple of routed ports on your 3750s, so there is no spanning tree involved and test to see if there is improvement.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...