llowing configuration associated with it: admin-context admin context admin allocate-interface Managemento/o config-url disko:/admin.cfg Adding a new context is as easy as using the context command, though the context won't work right away: ASA-5540 (config)# context GAD-Tech Creating context 'GAD-Tech' Done. (4) Notice that we're now in context configuration mode: ASA-5540(config-ctx)# Next, we can allocate some physical interfaces to the context: ASA-5540(config-ctx)# allocate-interface go/o ASA-5540(config-ctx)# allocate-interface g0/1 We aren't limited to physical interfaces. We can allocate subinterfaces to contexts as well. Simply append a subinterface identifier like this: 540(config-ctx)# allocate-interface g0/1.100 We still can't change to the context yet, and this gets me every single time: ASA-5540# changeto context GAD-Tech ERROR: Context hasn't been initialized with "config-url" We must manually configure a file where the configuration for our context will be saved: ASA-5540(config)# context GAD-Tech ASA-5540(config-ctx)# config-url disko:/gad-tech.cfg INFO: Context GAD-Tech was created with URL disko:/gad-tech.cfg We can see the status of all the contexts from within the system context with the show context command. Here we can see our newly created context in addition to the default admin context: ASA-5540# show context Context Name Class Interfaces *admin default Managemento/o disko:/admin.cfg Managing Contexts GAD-Tech default GigabitEtherneto/o, disko:/gad-tech.cfg GigabitEtherneto/1 default GigabitEtherneto/o, disko:/test.cfg GigabitEtherneto/2 Total active Security Contexts: 3 I added the test context after I added GAD-Tech to show that both of these contexts have interface G0/0 allocated to them. This is indicative of the shared interface scenario we talked about previously. Now let's enter the GAD-Tech context. We do this with the changeto command. Some Nexus switches support Virtual Device Contexts (VDCs), which are similar in principle to the contexts we're dealing with here. Just to confu