Native IOS Mode Configuration

Native IOS Mode Configuration

Figure 18-3 extends the discussion in the previous section to present a conceptual diagram of the Catalyst 6000 Native IOS Mode.

Figure 18-3. Conceptual Diagram of the MSFC Native IOS Mode
native-ios-mode-configuration-18.3

In Figure 18-3, the Gigabit Ethernet ports on the Supervisor (1/1 and 1/2) have been configured as fully routed interfaces. Slot 5 contains a Fast Ethernet line card. Ports 5/1–5/3 have been configured as Layer 2 switchports in VLAN 2. Ports 5/4–5/6 have been configured as switchports in VLAN 3. Port 5/10 has been configured as an 802.1Q trunk. Summarized configuration examples are also illustrated in the figure. As shown in Figure 18-3, the Native IOS mode centers around the concept of a virtual router. Physically routed ports such as Gigabit Ethernet 1/1 and 1/2 directly connect to the virtual router.

In the case of switchports, they connect to the router via an SVI. The SVI acts as a logical bridge/switch for the traffic within that VLAN. It is also assigned the Layer 3 characteristics of that VLAN for the purpose of connecting to the virtual router. Trunk links use the magic of ISL and 802.1Q encapsulation to simultaneously connect to multiple VLANs and SVIs.

The sections that follow walk step-by-step through a complete MSFC Native IOS Mode configuration that is similar to the MSM and MSFC configurations shown in Example 18-2 and Example 18-4.

The steps for completing the MSFC Native IOS Mode configuration are as follows:

  1. Assign a name to the router
  2. Configure VTP
  3. Create the VLANs
  4. Configure the Gigabit Ethernet uplinks as routed interfaces
  5. Configure the VLAN 2 switchports
  6. Configure the VLAN 3 switchports
  7. Configure a trunk switchport
  8. Configure the SVI interfaces
  9. Configure routing

Figure 18-4 illustrates the resulting configuration.

Figure 18-4. Conceptual Diagram for Configuration Example
native-ios-mode-configuration-18.4

Step 1: Assign a Name to the Router

Using the commands shown in Example 18-15, assign a name to the Catalyst Supervisor.

Example 18-15 Assigning a Name to the Catalyst

Step 2: Configure VTP

Configure VTP to place the Catalyst in VTP transparent mode and to use a VTP domain of Skinner as displayed in Example 18-16.

Example 18-16 Configuring VTP

Step 3: Create the VLANs

Create VLANs 2 and 3 in the VLAN database (VLAN 1 exists by default). Use the exit command to apply the VLAN and VTP changes and return to EXEC mode. This is shown in Example 18-17.

Example 18-17 Creating Two New VLANs

  • Tip
    The apply command can be used to apply the VTP and VLAN changes without leaving the vlan database mode.

Step 4: Configure the Gigabit Ethernet Uplinks As Routed Interfaces

The Gigabit Ethernet uplinks 1/1 and 1/2 are used to connect to the remainder of the network. To maximize Layer 3 hierarchy and scalability, these ports function as routed interfaces. Enter the commands shown in Example 18-18 to complete this task.

Example 18-18 Configuring the Uplink Ports as Routed Interfaces

Step 5: Configure the VLAN 2 Switchports

Ports 5/1–5/3 are used as access ports for server connections in VLAN 2. Example 18-19 illustrates these steps.

Example 18-19 Configuring the Access Ports in VLAN 2

  • Tip
    When creating similar configurations across many different ports, use the interface range command discussed in the “Useful Native IOS Mode Commands” section later in this chapter.

Step 6: Configure the VLAN 3 Switchports

Ports 5/4 and 5/5 are used as access ports for servers in VLAN 3. The commands shown in Example 18-20 can be used to provide this.

Example 18-20 Configuring the Access Ports in VLAN 3

Step 7: Configure a Trunk Switchport

Port 5/7 is used to carry all three VLANs to Cat-B, a Layer 2 Catalyst. The trunk uses 802.1Q encapsulation with VLAN 1 acting as the native VLAN. The commands in Example 18-21 can be used for this configuration.

Example 18-21 Configuring a Trunk Switchport

Step 8: Configure the SVI Interfaces

The MSFC requires three SVI interfaces to provide routing services for all three VLANs. As in Example 18-3 and Example 18-6, this configuration uses HSRP on VLANs 1 and 2. All three are configured with IPX network numbers. This is illustrated in Example 18-22.

Example 18-22 Configuring the SVI Interfaces

Step 9: Configure Routing

The commands shown in Example 18-23 can be used to configure the MSFC with EIGRP as an IP routing protocol (IPX uses IPX RIP by default).

Example 18-23 Configuring EIGRP as a Routing Protocol

About the author

Scott

Leave a Comment