It seems to me that private vlans are easier to set up and use less processor, and that's the advantage over using access-lists to prevent routing between vlans (when needed). Are there reasons to perhaps use access lists instead?
Good day! If hosts from these VLANs are not to connect with each other, you can use Private VLANs. But if in one way or another, interaction with hosts on these different VLANs would be required, you would definitely require some security. Access list is the most basic form of security incorporated in the IOS. Access list provides diffrent levels of security such as interface, port and even application. With access lists, you're actually separating them L3 to L7 as compared to private VLANs wherein you completely block them via L2.
Private vlans are used when you want to control traffic between hosts/servers that are on the same vlan. They allow you to segregate hosts or groups of hosts from each other while still using the same IP subnet addressing.
if you want to conrol traffic between vlans then asd you say you would use access-lists on your SVI's.
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 ...