e protocol is down Available but not configured via nameif Interface GigabitEthernet0/1.100 "", " is down, line protocol is down Available but not configured via nameif Interface GigabitEtherneto/2 "", is down, line protocol is down Available but not configured via nameif We cannot change any physical characteristic for an interface from within any context except the system context. Of course, I forget that every time and stare at the screen like I just caught a glimpse of the Matrix for the first time (whoa!), but then I remember that I have to change to the system context to change speed and duplex. This may seem like a silly limitation, but think about the case where a single interface is shared between multiple contexts. We wouldn't want a customer in one context to be able to change the speed on the shared interface, thus bringing down all of the other contexts for which he doesn't have control. Once you see the interfaces within a context, you can configure them with IP addresses, names, priorities, and most of the usual interface requirements. Write Mem Behavior When you issue the write memory command from within a context, it saves only that context's configuration. Similarly, when you're in the system context, issuing the write mem command will save only the system context's configuration. There is no indication that we are only saving the system context, but this behavior is consistent within all contexts. Managing Contexts The write mem command saves only the context from which you issued the command. ASA-5540(config)# wri mem Building configuration Cryptochecksum: 60a2296d 904d7bb1 f2e9284a 5576c1dd 1023 bytes copied in 3.320 secs (341 bytes/sec) One of the benefits of being in the system context is that we can save the configurations of all the contexts at once using the write mem all command: ASA-5540(config)# wri mem all Building configuration Saving context : system : (000/003 Contexts saved) Cryptochecksum: 60a2296d 904d7bb1 f2e9284a 5576c1dd 1023 bytes copied in 3.320 secs (341 bytes/sec) Saving