Table Of Contents

SBC Configuration Prerequisites

Installing SBC PIE on the MSB

Assigning an SBC Service Role

Creating and Assigning an SBC Service to a Service Card

Defining an SBC SVI and IP Address for the Interface

Enabling Routing for SVI

Verifying MSB Status as Active SBC Services Card

SBC Configuration Prerequisites

---

The SBC application runs both on a Multiservice Blade (MSB) and Distributed Route Processor (DRP). The MSB maintains a primary role as the SBC services card. For information on deploying the SBC on the DRP see the "SBC on the Cisco Carrier Routing System" module.

The following sections provide details and references for installing the package installation envelope (PIE) service package and completing the configuration for the MSB to function as a services card:

•Installing SBC PIE on the MSB

•Assigning an SBC Service Role

•Creating and Assigning an SBC Service to a Service Card

•Defining an SBC SVI and IP Address for the Interface

•Enabling Routing for SVI

•Verifying MSB Status as Active SBC Services Card

Feature History for Implementing SBC Configuration Prerequisites

Release	Modification
Release 3.3.0	SBC was introduced on the Cisco XR 12000 Series Router.
Release 3.4.0	SBC application is supported on the MSB.
Release 3.5.0	SBC application is supported on the Cisco CRS-1. For more information, see the "SBC on the Cisco Carrier Routing System" module.
Release 3.5.1	No modification.
Release 3.6.0	No modification.

Installing SBC PIE on the MSB

For details on installing and activating the SBC PIE on the MSB, see the Upgrading and Managing Cisco IOS XR Software module in the Cisco IOS XR Getting Started Guide.

Assigning an SBC Service Role

Use the steps in this section to assign a service role to a service card.

SUMMARY STEPS

1. configure

2. hw-module service sbc location prefer-active node-id

3. hw-module service sbc location prefer-standby node-id

4. commit

5. show services role

DETAILED STEPS

	Command or Action	Purpose
Step 1	configure Example: RP/0/0/CPU0:router# configure	Enables global configuration mode.
Step 2	hw-module service sbc location prefer-active node-id Example: RP/0/0/CPU0:router(config)# hw-module service sbc location 0/2/cpu0	Assigns the SBC service role to the preferred active card. Note Before you proceed to the next step, wait for the preferred active card to boot up with the SBC service role configured.
Step 3	hw-module service sbc location prefer-standby node-id Example: RP/0/0/CPU0:router(config)# hw-module service sbc location 0/4/cpu0	Assigns the SBC service role to the preferred standby card. Note Before you proceed to the next step, wait for the preferred standby card to boot up with the SBC service role configured.
Step 4	commit Example: RP/0/0/CPU0:router(config)# commit	Saves configuration changes. Use the commit command to save configuration changes to the running configuration file and remain within the configuration session.
Step 5	show services role Example: RP/0/0/CPU0:sbc3# show services role	Shows the service role for each service card. Node Configured Role Enacted Role Enabled Services --------------------------------------------------- 0/2/CPU0  SBC           SBC            SBC 0/4/CPU0 SBC          SBC           SBC

Creating and Assigning an SBC Service to a Service Card

This task defines how to create and assign an SBC service to a service card.

SUMMARY STEPS

1. configure

2. sbc service-name

3. service-location preferred-active node-id [preferred-standby node-id]

4. commit

DETAILED STEPS

	Command or Action	Purpose
Step 1	configure Example: RP/0/0/CPU0:router# configure	Enables global configuration mode.
Step 2	sbc service-name Example: RP/0/0/CPU0:router(config)# sbc mysbc	Creates a new SBC service and enters SBC configuration mode or enters the configuration mode of an existing service. Use the service-name argument to define the name of the service.
Step 3	service-location preferred-active node-id [preferred-standby node-id] Example: RP/0/0/CPU0:router(config-sbc)# service-location preferred-active 0/2/CPU0	Assigns the SBC service a primary and optionally, a secondary service location.
Step 4	commit Example: RP/0/0/CPU0:router(config-sbc)# commit	Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Defining an SBC SVI and IP Address for the Interface

This task defines an SBC Service Virtual Interface (SVI) and IP address for the interface. The SVI is created on the route processor (RP) card.

SUMMARY STEPS

1. configure

2. interface sbc number

3. ipv4 address

4. service-location preferred-active node-id [preferred-standby node-id]

5. commit

DETAILED STEPS

	Command or Action	Purpose
Step 1	configure Example: RP/0/0/CPU0:router# configure	Enables global configuration mode.
Step 2	interface sbc number Example: RP/0/0/CPU0:router(config)# interface sbc1	Enters the mode of an SBC interface, creating it if necessary. The argument number must be between 1 and 2000.
Step 3	ipv4 address address prefix Example: RP/0/0/CPU0:router(config-if)# ipv4 address 99.99.109.10 255.255.255.0	Assigns an IPv4 address to an SBC interface.
Step 4	service-location preferred-active node-id [preferred standby node-id] Example: RP/0/0/CPU0:router(config-if)# service-location preferred-active 0/2/CPU0	Attaches an SBC service interface to an SBC service.
Step 5	commit Example: RP/0/0/CPU0:router(config-if)# commit	Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Enabling Routing for SVI

This task enables routing for SVI. The example below uses the Intermediate System-to-Intermediate System (IS-IS) routing protocol. Any other routing protocol can be used instead.

SUMMARY STEPS

1. configure

2. router isis name

3. interface sbc number

4. passive

5. address-family ipv4 type

6. commit

DETAILED STEPS

	Command or Action	Purpose
Step 1	configure Example: RP/0/0/CPU0:router# configure	Enables global configuration mode.
Step 2	router isis instance-id Example: RP/0/0/CPU0:router(config)# router isis coresbc1 RP/0/0/CPU0:router(config-isis)#	Enables theIntermediate System-to-Intermediate System (IS-IS) routing protocol and specifies an IS-IS instance. This example uses the IS-IS routing protocol. Any other routing protocol can be used instead.
Step 3	interface sbc number Example: RP/0/0/CPU0:router(config-isis)# interface sbc1 RP/0/0/CPU0:router(config-isis-if)#	Configures the IS-IS protocol on an interface, for SBC. If necessary, the interface is created. The argument number must be between 1 and 2000.
Step 4	passive Example: RP/0/0/CPU0:router(config-isis-if)# passive	Suppresses IS-IS packets from traveling to the interface.
Step 5	address-family ipv4 [unicast] Example: RP/0/0/CPU0:router(config-isis-if)# address-family ipv4 unicast	Enters address family configuration mode for configuring IS-IS routing that uses standard IP Version 4 (IPv4) and IP Version 6 (IPv6) address prefixes.
Step 6	commit Example: RP/0/0/CPU0:router(config-if)# commit	Saves configuration changes. Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Verifying MSB Status as Active SBC Services Card

To verify that the converted and configured MSB is properly running SBC services, run one of the following commands:

show platform [node-id]	Displays information and status on each node (or specified node, if applicable) in the system. Run this command from the RP card's EXEC command mode
show processes sbcsvimgr	Displays the running SBC processes available and active on the SBC services card. Run this command from MSB EXEC command mode.