se us all, Cisco decided that the command to change between ASA contexts is switchto, while the command to change between Nexus VDCs is changeto. If you're working with me in a data center that has both, count on lots of profanity while I continuously use the wrong command on both platforms. First we'll change to the GAD-Tech context: ASA 5540# changeto context GAD-Tech Notice that the prompt has changed from hostname# to hostname/context#. This be- havior is configurable, but I like to leave it as-is because I find it useful. Next, from within the context, we can see that the output of the show context command is now limited to what can be seen from within the context: ASA-5540/GAD-Tech# sho context Context Name Class Interfaces GAD-Tech default GigabitEtherneto/o, disko:/gad-tech.cfg GigabitEtherneto/1 To change back to the system context, use the changeto system command: ASA-5540/GAD-Tech# changeto system ASA-5540# Once again, if you're used to Nexus VDCs, you might be frustrated in the ASA. The Nexus supports the command switchback, which sends you back from whence you came. The ASA has no changeback command. If we exit the context without using the changeto system command, we will return to the system context, but we will no longer be in enable mode: ASA-5540/GAD-Tech# exit Logoff Chapter 28: ASA Firewall Configuration Type help or '?' for a list of available commands. ASA-5540> Interfaces and Contexts Once an interface has been allocated to a context, it appears within that context. For example, this ASA 5540 has four interfaces: G0/0-3. Here is the system context con- figuration for the GAD-Tech context, where I have allocated GO/O, G0/1.100 and G0/2 to the context: ASA-5540# sho run context GAD-Tech context GAD-Tech allocate-interface GigabitEtherneto/0 allocate-interface GigabitEthernet0/1.100 allocate-interface GigabitEtherneto/2 config-url disko:/gad-tech.cfg From within the context, it appears as if only those interfaces exist: ASA-5540/GAD-Tech# sho int Interface GigabitEtherneto/o "", , is down, lin