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 packet processing card is active before you configure system elements. Refer to System Settings in this guide for information and instructions on activating packet processing cards.

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.

IMPORTANT:

We recommend that if your system is using Fast Ether Line Cards (FELCs, Ethernet 10/100), at least one context be configured per physical port in order to ensure adequate bandwidth for subscriber sessions.

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 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 line card is installed. This could be any number from 17 to 23, or 26 to 39, or 42 to 48.
  • For port ethernet port#, on FELCs, this value can be from 1 to 8. For the GELC/GLC2s and XGLCs this value must be 1. For for QGLCs enter a value from 1 to 4.
  • Optional: In the Ethernet Port configuration mode, add the preferred slot slot# command if line card port redundancy was enabled at the card level and you want to specify a port preference.
  • Optional: In the Ethernet Port configuration mode, configure the port speed, if needed, by entering the medium command. Refer to the Command Line Interface Reference for a complete explanation of this command.
  • 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 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 17/1 untagged, ifIndex 285278209)
    
    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
    
    L3 monitor LC-port switchover:  Disabled
    
    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 line card on which the physical port resides. slot# can be any integer value from 17 to 39, and 42 to 48. This command produces an output similar to that displayed in the following example that shows the configuration for port 1 on the line card installed in chassis slot 17. In this example, the port is bound to an interface called rp1 configured in a context called source.
    config
    
       port ethernet 17/1
    
          description LC17/1_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     SPIO1
    
    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.

ATM Interfaces and Ports

This section describes the minimum configuration required to use IP over ATM (IPoA) through an Optical ATM line card (OLC/OLC2). The procedures describe how to:

  1. Set the framing method for a specific OLC-type line card and make the card “active” by using the procedure defined in Enabling the OLC (ATM) Line Card.
  2. Create an IP over ATM interface (PVC interface) by following the example configuration in Creating an IP Interface for Use with an ATM Port.
  3. Enable the ATM port, create the IPoA (PVC) interface for the ATM port, and enable the PVC by applying the example configuration in Configuring an ATM Port to Use an IP Interface. Steps 2 and 3 together configure the data plane.
  4. Configure an ATM port to use with an SS7 link ID by applying the example configuration in Configuring an ATM Port for an SS7 Link. Step 4 configures the control plane through an SS7/IPoA (PVC) interface.

    IMPORTANT:

    Do not attempt to bind the link at this time. Complete the rest of the procedure (steps 5, 6, and 7) and return to bind the link to the port. The SS7 link can only be bound to the ATM port after the configuration for the SS7 routing domain has been completed as described in the 3G SGSN Configuration section of the SGSN Administration Guide.

  5. Configure the appropriate timing source (BITS from the SPIO or line-timing from an attached remote) to ensure transmit synchronization by applying the example configuration in the Configuring Transmit Timing Source section of System Settings.
  6. Verify the port and interface configuration as described in Verifying Port and Interface Configuration.
  7. Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Enabling the OLC (ATM) Line Card

Use the following example to select an OLC and set the framing type:

configure
   card slot#
      framing { SDH | SONET } 
      no shutdown
      end
Notes:
  • The default framing type is SONET (Synchronous Optical Network) for an Optical (ATM) line card.
  • Setting the framing method is required to make the card operational.
  • Entering no shutdown makes the card active.

Creating an IP Interface for Use with an ATM Port

Use the following example to create an IP interface to use with ATM:

configure
   context ctxt_name
      interface intf_name point-to-point
         ip address ip_addr net_mask
         ip address ip_addr net_mask secondary
         end
Notes:
  • The context must be the one in which you have or will configure the SGSN service.
  • You must enter the point-to-point keyword to create the PVC (Permanent Virtual Connection) interface for the IP over ATM.

Configuring an ATM Port to Use an IP Interface

Use the following example to configure an ATM port to use with an IP interface:

configure
   port atm slot#/port#
      no shutdown
      pvc vpi vpi_num vci vci_num
         no shutdown
         bind interface ifc_name ctx_name
         end
Notes:
  • The context must be the one you used when creating the IP interface (PVC) for the ATM port.

Configuring an ATM Port for an SS7 Link

Use the following example to configure an ATM port to use with an SS7 (Signalling System No. 7) link:

configure
   port atm slot#/port#
      no shutdown
      pvc vpi vpi_num vci vci_num
         no shutdown
         end
Notes:
  • The PVC for the SS7 link has been created but can not be bound unless the SS7 routing domain configuration has already been completed (see the SGSN Administration Guide).
  • Complete optional ATM port configuration (see the ATM Port Configuration Mode Commands chapter in the Command Line Interface Reference) and the other steps in this procedure to set timing and save the configuration.

Binding an SS7 Link to an ATM Port

Use the following example to bind an already configured SS7 link to a PVC interface for an ATM port:

configure
   port atm slot#/port#
      pvc vpi vpi_num vci vci_num
         bind link ss7-routing-domain ss7rd_id linkset-id id link-id id
         end
Notes:
  • Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Verifying Port and Interface 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 interface
    
    context_name represents the name of the context in which the interface was created. The output from these commands should look similar to that displayed in the following example. In this example an interface named mgmt1 was configured in the local context.
    Intf Name:       ipoa
    
    Intf Type:       Point
    to point
    
    IP State:        UP (Bound
    to 31/1 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:
    show configuration
    port slot#/port#
    
    This command produces an output similar to that displayed in the following example:
    config
    
       port atm 31/1
    
          no shutdown
    
          pvc vpi 121 vci
    4444
    
              no shutdown
    
              bind interface
    ipoa sgsn3g
    
           #exit
    
        #exit
    

Frame Relay Interfaces and Ports

This section shows the minimum configuration required to configure a frame relay interface on a channelized line card. To create and configure the frame relay interfaces and ports:

  1. Select a channelized line card (CLC/CLC2) and set the framing method by applying the example configuration in Setting the Characteristics of the Channelized Line Card.
  2. Configure the path, framing, mapping, Frame Relay characteristics, and the data link connection identifiers (DLCIs) as illustrated in the example configuration in Configuring the Channel Characteristics.
  3. Configure the appropriate timing source (BITS from the SPIO or line-timing from attached remote) to ensure transmit synchronization by applying the example configuration in the Configuring Transmit Timing Source section in System Settings.

    IMPORTANT:

    Before you can move to Step 4 to bind a DLCI to a port, you must complete the link configuration by configuring Peer-NSEIs and/or SS7 routing domains as described in SGSN Service Configuration Procedures in the SGSN Administration Guide. Return to this procedure when your link configuration is complete.

  4. Bind the link to the port by applying the example configuration in the section for Binding a DLCI.
  5. Verify the card, port and link configuration and status with the commands illustrated in the verification examples below.
  6. Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Setting the Characteristics of the Channelized Line Card

Use the following example to set the operational characteristics, the framing type, the header type, the service type, and the boot time E1 framing type, for the Frame Relay Channelized Line Card (CLC):

configure
   card slot
      framing framing_type [ ds1 | e1 ]
      header-type { 2-byte | 4-byte } 
      initial-e1-framing { crc4 | standard } 
      service-type
frame-relay 
      no shutdown
      end
Notes:
  • Make a note of the information you configure - you will need it again later for the path command used to configure channel characteristics.
  • The default framing_type is SONET for the channelized line card.
  • With releases 8.1 and higher, we recommend that you include the signal type, either ds1 (24 timeslots, 1.536 Mbps) or e1 (32 timeslots, 2.048 Mbps), when defining the framing.
  • With releases 8.1 and higher, you need to set the service-type for the CLC card to frame-relay. All other options are not fully supported at this time.

Configuring the Channel Characteristics

Use the following example to configure the path, framing, mapping, timeslots, and the Frame Relay interface and LMI characteristics for a specific CLC/CLC2 port:

configure
   port channelized slot#/port#
      path path_id { ds1 | e1 } number_of_connections frame_mapping multiplex# multiplex# framing framing_mode mapping-mode mapping_mode [ timeslots timeslot# [ timeslot# ]  ]

IMPORTANT:

You should record the path definition values you enter as the information will be needed again with other configuration commands.

      frame-relay
path path_id { ds1 | e1 } number_of_connections [ timeslot timeslot# [ intf-type  intf_type [ lmi-type lmi_type ] ] ]
      dlci path path_id { ds1 | e1 } number_of_connections { dlci dlci_id | timeslot timeslot# } 
      no shutdown
      end

Binding a DLCI

Use the following procedure to bind the data link connection identifier (DLCI) to the channelized (Frame Relay) port.

IMPORTANT:

This procedure should not be attempted until after the configuration is completed for Peer-NSEIs and/or SS7 routing domains as described in the SGSN Administration Guide.

configure
   port channelized port#
      bind link { peer-nsei nse_id ns-vc-id nsvc_id | ss7-routing-domain ss7rd_id linkset-id id link-id id}
      end

Verifying the Frame Relay Interface Configuration and Status

Several commands generate display outputs that provide information about the Frame Relay card, port, DLCI and link configurations. The most commonly used commands are illustrated below. All of these commands are issued from the Exec mode.

Display Port and DLCI Configuration Details

[local]host_name# show port info 27/1
Port: 27/1
  Port
Type                    : STM1/OC3 Channelized
  Description                  : (None Set)
  Controlled
By Card           : 11 (Packet
Services Card)
  Redundancy
Mode              : Port Mode
  Framing
Mode                 : SDH
  Redundant
With               : Not Redundant
  Preferred
Port               : Non-Revertive
  Physical
ifIndex             : 453050368
  Administrative
State         : Disabled
  Link
State                   : Unknown
  Line
Timing                  : Yes
  SFP
Module                   : Not Present
  Path
1 e1 1                  : tu12-au3
1/1 crc4 bit-async
    Timeslots                  : 12-14
    Frame
Relay Intf Typ       : DCE
    Frame
Relay LMI Type       : Q933A
    Frame
Relay LMI n391       : 6
    Frame
Relay LMI n392       : 2
    Frame
Relay LMI n393       : 2
    Frame
Relay LMI t391       : 10
    Frame
Relay LMI t392       : 15
      Frame
Relay DLCI 243
        Logical
ifIndex        : 453050369
        Admin
State            : Disabled
        Operational
State      : Down, Standby
      Shaping                  : WFQ: Weight 1
      Number
of DLCI           : 1
      Reserved
Bandwidth       : 0
of 192000 bits/sec
  Path
1 e1 2                  : Unused
  Number
of DLCI               : 1

Display Port and DLCI Configuration and Status

The following display is only a partial output of the show command to illustrate the channelized port and DLCIs.

[local]host_name# show port table 
Port  Type                    Admin     Oper  Link  State     Redundant
With
----  ----------------------  --------  ----  ----  --------  --------------
27/1  STM1/OC3
Channelized    Enabled    -    Up    -        None
      FR DLCI   1  1  1  52   Enabled   Up    -     Active     -
      FR DLCI   1  2  1  53   Enabled   Down   -     Active     -