YES. CONTEXT ARE CREATED AND CONFIGURATIONS AS WELL.
BELOW IS ONE CONTEXT CONFIG.
CONTEXT_A
sh run
: Saved
:
ASA Version 7.0(7)
!
hostname CONTEXT_A
enable password xxx
names
dns-guard
!
interface GigabitEthernet0/0.2
nameif outside_b
security-level 0
ip address 192.168.13.211 255.255.255.0
!
interface GigabitEthernet0/1.2
shutdown
no nameif
security-level 0
no ip address
!
interface GigabitEthernet0/2.2
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/3.2
nameif inside_b
security-level 100
ip address 10.10.100.254 255.255.255.0
!
passwd xxxy
access-list outside_b_access_in extended permit icmp any any
access-list outside_b_access_in_V1 extended permit icmp any any
pager lines 24
mtu outside_b 1500
mtu inside_b 1500
no asdm history enable
arp timeout 14400
global (outside_b) 20 192.168.13.212
nat (inside_b) 20 10.10.100.0 255.255.255.0
access-group outside_b_access_in_V1 in interface outside_b
route outside_b 0.0.0.0 0.0.0.0 192.168.13.1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00
timeout mgcp-pat 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
no snmp-server location
no snmp-server contact
telnet timeout 5
ssh timeout 5
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map global_policy
class inspection_default
inspect dns maximum-length 512
inspect ftp
inspect h323 h225
inspect h323 ras
inspect netbios
inspect rsh
inspect rtsp
inspect skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect tftp
inspect sip
inspect xdmcp
!
service-policy global_policy global
Cryptochecksum:xxx
: end
