<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Context Mode in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/context-mode/m-p/989198#M939004</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that is correct....thks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Apr 2008 17:02:08 GMT</pubDate>
    <dc:creator>sonic7771</dc:creator>
    <dc:date>2008-04-18T17:02:08Z</dc:date>
    <item>
      <title>Context Mode</title>
      <link>https://community.cisco.com/t5/network-security/context-mode/m-p/989196#M939002</link>
      <description>&lt;P&gt;i have an ASA5510 trying to configure multiple IP's to outside interface but cannot. I have it on my pix515 but do not know how to do it in ASA device. i am using my CLI config from the 515 to figure out in the GUI for the ASA&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:33:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/context-mode/m-p/989196#M939002</guid>
      <dc:creator>sonic7771</dc:creator>
      <dc:date>2019-03-11T12:33:40Z</dc:date>
    </item>
    <item>
      <title>Re: Context Mode</title>
      <link>https://community.cisco.com/t5/network-security/context-mode/m-p/989197#M939003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are you saying you want to have multiple ip address on your outside interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Apr 2008 16:53:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/context-mode/m-p/989197#M939003</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-04-18T16:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: Context Mode</title>
      <link>https://community.cisco.com/t5/network-security/context-mode/m-p/989198#M939004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that is correct....thks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Apr 2008 17:02:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/context-mode/m-p/989198#M939004</guid>
      <dc:creator>sonic7771</dc:creator>
      <dc:date>2008-04-18T17:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Context Mode</title>
      <link>https://community.cisco.com/t5/network-security/context-mode/m-p/989199#M939005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can  create subinterfaces on an appliance to have multiple IP's on the outside interface, you can use the interface command followed by the interface name and the subinterface number, as shown in the following syntax: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface physical_interface.subinterface &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here, physical_interface is the actual physical interface and subinterface is an integer between 1 and 4,294,967,295. Example 4-13 demonstrates how to create a subinterface 300 on GigabitEthernet0/0. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 4-13. Creating a Subinterface &lt;/P&gt;&lt;P&gt;Chicago# configure terminal &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config)# interface GigabitEthernet0/0.300 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have created a subinterface, the next step is to associate the interface with a unique VLAN identity. Assign a VLAN ID by using the vlan subinterface configuration command followed by the actual VLAN ID, which ranges between 1 and 4096. In Example 4-14, the administrator has linked GigabitEthernet0/0.300 to vlan 300. Although the subinterface number and the VLAN ID do not have to match, it is a good practice to use the same number for ease of management. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 4-14. Associating a VLAN ID to a Subinterface &lt;/P&gt;&lt;P&gt;Chicago# configure terminal &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config)# interface GigabitEthernet0/0.300 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config-if)# vlan 300 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Caution &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the main physical interface is shut down, all the associated subinterfaces are disabled as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The subinterface is configured identically to a physical interface, using the nameif, security-level, and ip address commands. It does not, however, allow the use of speed and duplex commands, discussed in the previous section. Example 4-15 shows a subinterface GigabitEthernet0/0.300 configuration that is set up as a DMZ interface with the security level 30 and an IP address of 192.168.20.1/24 in VLAN 300. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 4-15. Configuring Subinterface Parameters &lt;/P&gt;&lt;P&gt;Chicago# configure terminal &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config)# interface GigabitEthernet0/0.300 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config-if)# vlan 300 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config-if)# nameif DMZ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config-if)# security-level 30 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chicago(config-if)# ip address 192.168.20.1 255.255.255.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2008 09:24:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/context-mode/m-p/989199#M939005</guid>
      <dc:creator>francisco_1</dc:creator>
      <dc:date>2008-04-21T09:24:31Z</dc:date>
    </item>
  </channel>
</rss>

