There’s a requirement to separate networks within an organization. What technology can be used while preserving hardware?
A. Virtual Context
B. VRF
C. Other option
What technology can be used while preserving hardware?
There’s a requirement to separate networks within an organization. What technology can be used while preserving hardware?
A. Virtual Context
B. VRF
C. Other option
Wording is tricky/lacking detail. The VDCs (Virtual Device Contexts) on Nexus 7k can effectively virtualize the device, including any VRFs the tenant admin wishes to deploy.
https://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-10-slot-switch/White_Paper_Tech_Overview_Virtual_Device_Contexts.html
But it’s a long stretch, I’d stick with VRF (B) as it is a more common option and the question does not involve DC switches
I would say VRF where networks are treated in separate routing tables and forwarding instances on the same hardware.
Virtual Context are described in the following document:
https://www.cisco.com/c/en/us/td/docs/app_ntwk_services/data_center_app_services/application_networking_manager/5-2-2/user/guide/User_Guide/UG_virtual_contexts.pdf
Virtual contexts use the concept of virtualization to partition your ACE into multiple virtual devices or
contexts. Each context contains its own set of policies, interfaces, resources, and administrators. This
feature enables you to more closely and efficiently manage resources, users, and the services you provide
to your customers.
There are two types of virtual contexts; the admin context and the user context. The ACE comes
preconfigured with the default Admin context, which you can modify but you cannot delete. From the
Admin context, you can create user contexts. You also use the Admin context to configure High
Availability (HA or fault tolerance between ACE devices), configure resource classes, and manage ACE
licenses.