System Interfaces and Ports

This chapter describes how to create a context and configure system interfaces and ports within the context. Before beginning these procedures, refer to your product-specific administration guide for configuration information for your product.

This chapter includes the following:

IMPORTANT:

Make sure at least one Data Processing Card (DPC) or Data Processing Card Universal (UDPC) is active before you configure system interfaces and ports. Refer to System Settings in this guide for information and instructions on activating DPCs.

Contexts

Even though multiple contexts can be configured to perform specific functions, they are all created using the same procedure.

Creating Contexts

IMPORTANT:

Commands used in the configuration examples in this section represent the most common or likely commands and/or keyword options. In many cases, other commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.

To create a context, apply the following example configuration:
configure
   context name
      end

Repeat to configure additional contexts.

Viewing and Verifying Contexts

  1. Verify that your contexts were successfully created by entering the following command:
    [local]host_name# show context all
    
    The output is a two-column table similar to the example below. This example shows that two contexts were created: one named source and one named destination.
    Context Name    ContextID    State
    
    ------------    ---------    -----
    
    local           1            Active
    
    source          2            Active
    
    destination     3            Active
    
    The left column lists the contexts that are currently configured. The center column lists the corresponding context ID for each of the configured contexts. The third column lists the current state of the context.
  2. Save your configuration as described in the Verifying and Saving Your Configuration chapter.
  3. Now that the context has been created, interfaces and specific functionality can be configured within the context. Proceed to other sections for instructions on configuring specific services and options.

Ethernet Interfaces and Ports

Regardless of the type of application interface, the procedure to create and configure it consists of the following:

  1. Create an interface and assign an IP address and subnet mask to it by applying the example configuration in Creating an Interface.
  2. Assign a physical port for use by the interface and bind the port to the interface by applying the example configuration in Configuring a Port and Binding It to an Interface.
  3. Optionally configure a static route for the interface by applying the example configuration in Configuring a Static Route for an Interface.
  4. Repeat the above steps for each interface to be configured.

    IMPORTANT:

    This section provides the minimum instructions for configuring interfaces and ports to allow the system to communicate on the network. Commands that configure additional interface or port properties are described in the Ethernet Port Configuration Mode Commands and Ethernet Interface Configuration Mode Commands chapters of the Command Line Interface Reference.

    CAUTION:

    To ensure that system line card and port-level redundancy mechanisms function properly, the Spanning Tree protocol must be disabled on devices connected directly to any system port. Failure to turn off the Spanning Tree protocol may result in failures in the redundancy mechanisms or service outage.

Creating an Interface

Use the following example to create a new interface in a context:

configure
   context name
      interface name
         { ip | ipv6 } address address subnetmask [ secondary ]
         end
Notes:
  • Optional: Add the loopback keyword option to the interface name command, to set the interface type as “loopback” which is always UP and not bound to any physical port.
  • Optional: Add the secondary keyword to the { ip | ipv6 } address command, to assign multiple IP addresses to the interface. IP addresses can be entered using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.
  • Optional: In the interface config mode, add the port-switch-on-L3-fail address command, to configure the interface for switchover to the port on the redundant line card if connectivity to a specified IP address is lost. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

Configuring a Port and Binding It to an Interface

Use the following example configuration to configure and assign a port to an interface:

configure
   port ethernet slot#/port#
      description description
      no shutdown
      bind interface interface_name  context_name
      end
Notes:
  • For port ethernet slot#, use the actual chassis slot in which the MIO/UMIO card is installed; this could be 5 or 6.
  • For port ethernet port#, use ports 10 to 19 (DC1) or 20 to 29 (DC2).
  • Optional: In the Ethernet Port configuration mode, add the preferred slot slot# command if you want to specify a port preference.
  • Binding associates the port and all of its settings to the named interface.

Configuring a Static Route for an Interface

Use the following example to configure a static route for an interface:

configure
   context name
       { ip | ipv6 } route ip_address netmask next-hop gw_address interface_name
      end
Notes:
  • ip_address and netmask are the IP address and subnet mask of the target network. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.
  • gw_address is the IP address of the default gateway or next-hop route. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.
  • To configure a route to the gateway router, use 0.0.0.0 for the network and mask variables.
  • Repeat as needed. Multiple static routes can be configured to the same destination to provide an alternative means of communication in case the preferred route fails.

Viewing and Verifying Port Configuration

  1. Verify that your interface configuration settings are correct by entering the following commands:
    [local]host_name# context context_name
    
    [context_name]host_name# show { ip | ipv6 } interface
    
    context_name represents the name of the context in which the interface was created. The output from these commands should be similar to the following example. In this example an interface named mgmt1 was configured in the local context.
    Intf Name:       mgmt1
    
    Intf Type:       Broadcast
    
    IP State:       
    UP (Bound to 5/11 untagged, ifIndex 285278209)
    
    IP Address:      192.168.100.3        Subnet Mask:     255.255.255.0
    
    Bcast Address:   192.168.100.255      MTU:             1500
    
    Resoln Type:     ARP                  ARP timeout:     3600
    secs
    
    Number of Secondary
    Addresses:  0
    
    Total interface count:          1
    
  2. Verify that your port configuration settings are correct by entering the following command:
    [context_name]host_name# show configuration
    port slot#/port#
    
    slot# is the chassis slot number of the MIO/UMIO on which the physical port resides. slot# can be 5 or 6. This command produces an output similar to that displayed in the following example that shows the configuration for port 11 on the MIO/UMIO installed in chassis slot 5. In this example, the port is bound to an interface called rp1 configured in a context called source.
    config
    
       port ethernet 5/11
    
          description MIO5/11_RP1
    
          no shutdown
    
          bind interface
    rp1 source
    
          #end
    
  3. Verify that your static route(s) was configured properly by entering the following command:
    [context_name]host_name# show ip static-route
    
    This command produces an output similar to that displayed in the following example that shows a static route to a gateway with an IP address of 192.168.250.1.
    Destination      Nexthop          Protocol  Prec  Cost  Interface
    
    0.0.0.0/0        192.168.250.1    Static      0    0     MIO1
    
    0.0.0.0/0        192.168.250.1    Static      0    0     rp1 source
    
  4. Save the configuration as described in the Verifying and Saving Your Configuration chapter.