System Element Configuration Procedures


System Element Configuration Procedures
 
This chapter presents interface and port configurations procedures. 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 Services Card (PSC) is active before you configure system elements. Refer to Configuring System Settings in this guide for information and instructions on activating PSCs.
Creating Contexts
Even though multiple contexts can be configured to perform specific functions, they are all created using the same procedure.
 
Important: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional 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
Notes:
Important: We recommend that if your system is using Ethernet 10/100 Line Cards, at least one context be configured per physical port in order to ensure adequate bandwidth for subscriber sessions.
 
Viewing and Verifying Contexts
Step 1
show context all
The output is a two-column table that looks similar to the example below. In this example, it shows that two contexts were created: one called source and one called 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.
Step 2
Save your configuration as described in the Verifying and Saving Your Configuration chapter.
Step 3
 
Creating and Configuring Ethernet Interfaces and Ports
Regardless of the type of application interface, the procedure to create and configure it consists of the following:
Step 1
Step 2
Step 3
Step 4
Important: This section provides the minimum instruction set for configuring interfaces and ports to allow the system to communicate on the network. Commands that configure additional interface or port properties are provided in the Ethernet Port Configuration Mode and Ethernet Interface Configuration Mode 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 address <address subnetmask> [ secondary ]
        end
Notes:
Option: Add the loopback keyword option to the interface <name> command, to set the interface type as “loopback”.
Option: Add the secondary keyword to the ip address command, to assign multiple IP addresses to the interface. IP addresses can be in IPv4 or IPv6 format.
Option: 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 can be in IPv4 or IPv6 format.
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.
Option: In the Ethernet Port configuration mode, add the preferred slot slot# command if LC port redundancy was enabled at the card level and you want to specific a port preference.
Option: 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.
Configuring a Static Route for an Interface
Use the following example to configure a static route for an interface:
configure
  context <name>
     ip 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.
gw_address is the IP address of the default gateway or next-hop route.
 
Viewing and Verifying Port Configuration
context <context_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: mgmt1
Intf Type: Broadcast
IP State: UP (Bound to 17/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
L3 monitor LC-port switchover: Disabled
Number of Secondary Addresses: 0
Total interface count: 1
 
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
#exit
end
 
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
Save the configuration as described in the Verifying and Saving Your Configuration chapter.
 
Creating and Configuring ATM Interfaces and Ports
This section describes the minimum configuration required to use IP over ATM through an Optical ATM line card (OLC). The procedures define how to create and to configure the IP interfaces, ATM interfaces, and the ATM ports:
Step 1
Step 2
Step 3
Steps 2 and 3 together configure the data plane.
Step 4
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.
Step 5
Step 6
Step 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 line card and set the framing type:
configure
  card <slot#>
     framing <SDH|SONET>
     no shutdown
     end
Notes:
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:
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:
Configuring an ATM Port for an SS7 Link
Use the following example to configure an ATM port to use with an SS7 link:
configure
  port atm <slot#>/<port#>
     no shutdown
     pvc vpi <vpi_num> vci <vci_num>
        no shutdown
        end
Notes:
Complete optional ATM port configuration (see the ATM Port Configuration Mode 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 Saving Your Configuration chapter.
 
Verifying Port and Interface Configuration
Step 1
 
context <context_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
Step 2
 
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
   #exitend
 
Creating and Configuring 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:
Step 1
Step 2
Important: Before you can move to Step 3, you must configure Peer-NSEI and/or SS7 routing domains as described in the 3G SGSN Configuration section of the SGSN Administration Guide. Complete Steps 4 and 5 and return to the procedure when your configuration is complete.
Step 3
Step 4
Step 5
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:
The default framing_type is SONET for the channelized line card.
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 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 make a record of the values you enter as the information will be needed again for additional configuration of the frame-relay command.
     frame-relay path <path_id> { ds1 | e1 } <number_of_connections> [ timeslot <timeslot#> [ intf-type <intf_type> [ lmi-type <lmi_type> ] ] ]
     no shutdown
     end
Configuring and Binding a DLCI
Use the following procedure to configure the data link connection identifier (DLCI) and bind the DLCI to the channelized (Frame Relay) port:
Important: This procedure should not be attempted until after the 2G SGSN configuration is completed for Peer-NSEIs and/or SS7 routing domains as described in the SGSN Administration Guide with command details in the Command Line Interface Reference.
configure
  port channelized <port#>
     dlci path <path_id> { ds1 | e1 } <number_of_connections> { dlci <dlci_id> | timeslot <timeslot#> }
        bind link { peer-nsei <nse_id> ns-vc-id <nsvc_id> | ss7-routing-domain <ss7rd_id> linkset-id <id> link-id <id>}
        end
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883