It seems to me that we are trying to make this more complicated than it needs to be. If this is the configuration:
Interface fastethernet 0/0
ip address 192.168.32.1 255.255.255.0
ip address 192.168.61.1 255.255.255.0 secondary
then it means that IP is being routed and something is being bridged that is not IP. If that is not the case then I hope that the original poster will clarify what is happening.
If the desire is to route IP and bridge some other protocol, then it should be enough to enable layer 2 on the interface(s) to do the switching/bridging and to configure a layer 3 SVI for routing IP. This should let the switch bridge the other traffic, which it will do by default and route the IP traffic.
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 ...