Configuring Security Context

Configuring Security Context

To ascertain a ambience mode, add, or change a ambience in the arrangement configuration, accomplish the afterward steps:

Step 1. Ascertain the ambience approach (single or multiple). Use the approach {single | multiple} command from

the all-around configuration. The apparatus will crave a reboot. Note that the approach agreement is

not stored in the agreement file.

Step 2. To add or adapt a ambience in the arrangement beheading amplitude or the admin context, use the context

{name} command from the all-around agreement approach to access the ambience submode. The prompt

changes to the afterward to announce it is still in the arrangement beheading amplitude and is modifying

parameters for the specific context:

hostname(config-ctx)#

Step 3. Specify the interface(s) allocated to a context. Access the command adapted for a physical

interface or for one or added subinterfaces application the allocate-interface command from the context

submode. Repeat these commands assorted times to specify altered ranges. Note that the

transparent firewall approach allows for alone two interfaces to canyon through traffic. Same interfaces can

be assigned to assorted contexts in baffled mode, if desired. Transparent approach does not allow

shared interfaces.

Step 4. Identify the URL from which the arrangement downloads the ambience agreement by application the configurl

command. Ambience agreement can be downloaded via several methods, such as internal

flash, HTTP/HTTPS, TFTP, or application FTP server.

Step 5. Change amid contexts to accomplish agreement and ecology tasks aural anniversary ambience by

using the changeto ambience {name} command. The alert changes to the following:

hostname/context-name#

Step 6. To appearance the ambience information, use the appearance ambience [name | detail| count] command.

Example 6-1 shows how to accredit assorted contexts mode. The archetype sets the admin-context to be

administrator, creates a ambience alleged "administrator" on the centralized beam memory, and adds addition two

contexts: a ambience alleged customerA from an FTP server, and addition ambience alleged customerB from internal

flash. Note that the ambience names are case sensitive.

Example 6-1. Configuring Assorted Contexts

Code View:

hostname(config)# approach multiple

hostname(config)# admin-context administrator

hostname(config)# ambience administrator

hostname(config-ctx)# allocate-interface Ethernet0.1

hostname(config-ctx)# allocate-interface Ethernet1.1

hostname(config-ctx)# allocate-interface Management0/0

hostname(config-ctx)# config-url flash:/admin.cfg

hostname(config-ctx)# ambience customerA

hostname(config-ctx)# allocate-interface Ethernet0.100 int1

hostname(config-ctx)# allocate-interface Ethernet0.102 int2

hostname(config-ctx)# allocate-interface Ethernet0.103-Ethernet0.108 int3-int8

hostname(config-ctx)# config-url ftp://joe:password@10.1.1.1/configs/

customerA.cfg

hostname(config-ctx)# ambience customerB

hostname(config-ctx)# allocate-interface Ethernet1.200 int1

hostname(config-ctx)# allocate-interface Ethernet1.202-Ethernet1.203 int2-int3

hostname(config-ctx)# allocate-interface Ethernet1.205-Ethernet1.210 int5-int10

hostname(config-ctx)# config-url flash:/customerB.cfg

Example 6-2 shows how to change amid contexts and the arrangement beheading amplitude in advantaged EXEC mode

to accomplish agreement and ecology tasks aural anniversary context. The arrangement beheading amplitude is the admin

context from area you can about-face amid the contexts. Ensure the location, because the configuration

changes fabricated are applicative to the accepted position (within the context). For example, back the show

running-config command is executed, it will affectation alone the accepted agreement of that ambience and not the

running configurations of all contexts (system additional all contexts).

Example 6-2. Changing Amid Contexts

hostname/admin# changeto system

hostname# changeto ambience customerA

hostname/customerA#

OR

hostname# changeto ambience customerB

hostname/customerB#