You are planning to isolate guest and IoT networks on campus. How can you configure separate routing tables and policies per tenant using HPE Aruba Networking Central?
A.
Configure separate routed interfaces on each access switch
B.
Configure separate Virtual Routing and Forwarding profiles
C.
Configure a single SVI profile for Guest, IoT and Employee traffic
Each VRF owns its own forwarding and routing table, allowing Guest, IoT and Employee segments to use separate default routes and route-import policies on supported switches. Associate the corresponding SVIs or routed interfaces with the intended VRF and control any deliberate inter-VRF leakage through explicit security mechanisms. An SVI on its own creates a Layer 3 interface but not an independent routing domain. Check DHCP relay, DNS access and upstream reachability per VRF, because control-plane separation does not automatically provision the services that each tenant needs. Where guest must reach a shared DNS server, use deliberate inter-VRF route leaking or firewall-controlled service access. A VRF does not automatically create a permitted path between tenant routing tables.
Routed interfaces by themselves do not establish separate routing-table instances. A single shared SVI profile cannot isolate tenant RIBs. Multiple VRFs create independent forwarding tables, with carefully controlled route leaking if cross-tenant access is required.
Official HPE references | Creating a VLAN Profile • Step 3—Configuring VLANs and Port Profiles | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit