Configuring the Connection

Table Of Contents

Configuring the Connection

How to Configure the Connection Mode

Options

Configuring the Connection Mode: Examples

How to Monitor the Connection Mode

Monitoring the Connection Mode: Example

How to Configure the Link Mode

About the Link Mode

Options

How to Configure Asymmetric Routing Topology

About Asymmetric Routing Topology

Asymmetric Routing and Other Service Control Capabilities

Enabling Asymmetric Routing

How to Monitor Asymmetric Routing

How to Configure a Forced Failure

How to Force a Virtual Failure

How to Exit from a Virtual Failure

How to Configure the Failure Recovery Mode

Options

Configure the Failure Recovery Mode: Examples

How to Configure the SCE Platform/SM Connection

About the SCE Platform/SM Connection

How to Configure the Behavior of the SCE Platform in Case of Failure of the SM

How to Configure the SM-SCE Platform Connection Timeout

How to Enable and Disable Link Failure Reflection

About Link Failure Reflection

How to Enable Link Failure Reflection

How to Disable Link Failure Reflection

How to Enable and Disable Link Failure Reflection on All Ports

How to Configure Link Failure Reflection in Linecard-Aware Mode (SCE 2000 only)

Configuring the Connection

• How to Configure the Connection Mode

• How to Monitor the Connection Mode

• How to Configure the Link Mode

• How to Configure Asymmetric Routing Topology

• How to Configure a Forced Failure

• How to Configure the Failure Recovery Mode

• How to Configure the SCE Platform/SM Connection

• How to Enable and Disable Link Failure Reflection

How to Configure the Connection Mode

The connection mode command allows you to configure the topology of the system in one command. The connection mode is determined by the physical installation of the SCE platform.

• Options

• Configuring the Connection Mode: Examples

Options

The following topology-related parameters are included in the connection mode command.

Note that some options are relevant for cascaded topologies only.

•Connection mode — Can be any one of the following, depending on the physical installation of the SCE platform:

–Inline — single SCE platform inline

–Receive-only — single SCE platform receive-only

–Inline-cascade — two cascaded SCE platforms inline

–Receive-only-cascade — two cascaded SCE platforms receive-only

•Default — inline

•Physically-connected-links — In cascaded topologies, defines which link is connected to this SCE platform.

Possible values are `link-0' and `link-1'.

Not applicable to single SCE platform topologies.

•Priority — This parameter defines which is the primary SCE platform. It is applicable only in a two SCE platform topology.

Possible values are `primary' and `secondary'

Not applicable to single SCE platform topologies.

•On-failure — This parameter determines whether the system cuts the traffic (cutoff) or bypasses it (bypass) when the SCE platform either has failed or is booting.

Default — bypass

Not applicable to receive-only topologies.

Note Do not change the connection mode unless the physical installation has been changed.

Step 1 From the SCE(config if)# prompt, type connection-mode inline|receive-only|inline-cascade|receive-only-cascadephysically-connected-links [link 0|link 1]priority [primary|secondary]on-failure [bypass|cutoff] and press Enter.

Configures the connection mode.

Configuring the Connection Mode: Examples

• Example 1

• Example 2

Example 1

This example defines the primary device in a two-SCE platform redundant, inline topology. Link 0 is connected to this device, and the link mode on failure is bypass.

SCE(config if)# connection-mode inline-cascade physically-connected-links link-0 priority primary on-failure bypass
Example 2

This example defines a single-SCE platform, dual link, receive-only topology. Neither link mode on failure, nor physically-connected-links, nor priority is applicable.

SCE(config if)# connection-mode receive-only

How to Monitor the Connection Mode

• Monitoring the Connection Mode: Example

Step 1 From the SCE>prompt, type show interface linecard 0 connection-mode and press Enter.

Displays the connection mode configuration.

Monitoring the Connection Mode: Example

The following example shows how to display the current configuration of the connection mode.

SCE>show interface linecard 0 connection-mode Connection mode is inline slot failure mode is bypass Redundancy status is standalone SCE>

How to Configure the Link Mode

• About the Link Mode

• Options

About the Link Mode

The SCE platform has an internal hardware card used to maintain the links even when the SCE platform fails. This hardware card has four possible modes of operation:

•bypass

•forwarding

•cutoff

•sniffing

Normally, the link mode is selected by the SCE platform software according to the configured connection-mode. However, the link-modecommand can be used to enforce a specific desired mode. This may be useful when debugging the network, or in cases where we would like the SCE platform just to forward the traffic. (Note that this is only relevant to inline topologies even though the configuration is available also when in receive-only mode.)

Options

The following link mode options are available:

•Forwarding — forwards traffic on the specified link to the SCE platform for processing.

•Bypass — stops all forwarding of traffic on the specified link to the SCE platform. Traffic still flows on the link, but is not processed in any way by the SCE platform.

This does not affect the redundancy states.

•Sniffing — allows the SCE platform to forward traffic on the specified link through the bypass mechanism while still analyzing the traffic passively.

Sniffing is permitted to be configured for all links, only (use the all-linksoption).

•Cutoff — completely cuts off flow of traffic through the specified link.

•link# — the number of the link being configured

Use the all-linksoption to apply the configuration to all links

Recommendations and restrictions

Note the following recommendations and restrictions:

•Since the SCE 1000 platform has only one link, the link is not specified.

•Since the SCE 2000 platforms have more than one link, it is required to specify the link. The link designations are different for the GBE and FE platforms, as follows:

–SCE 2000 4xGBE — GBE1-GBE2/GBE3-GBE4

–SCE 2000 4/8xFE — LINK1/LINK2

•Use the all-linksoption to configure the link mode for all links (SCE 2000 platforms only).

•It is recommended that both links be configured together. Use the all-linksoption.

•Link mode is relevant only to inline topologies.

•It is recommended that in cascaded topologies, both SCE platforms be configured for the same link mode, otherwise the service will be unpredictable.

•Sniffing can only be configured for all links, therefore, to configure sniffing, the all-links option is required, not just recommended.

•The default link mode is forwarding.

When other link modes are selected, active service control is not available and any service control configuration will not be applicable.

Step 1 From the SCE(config if)# prompt, type link-mode [ linknumber|all-links] [forwarding|bypass|sniffing|cutoff] and press Enter.

Configures the link mode for the specified link.

How to Configure Asymmetric Routing Topology

• About Asymmetric Routing Topology

• Asymmetric Routing and Other Service Control Capabilities

• Enabling Asymmetric Routing

• How to Monitor Asymmetric Routing

About Asymmetric Routing Topology

In some Service Control deployments, asymmetrical routing occurs between potential service control insertion points. Asymmetrical routing can cause a situation in which the two directions of a bi-directional flow pass through different SCE platforms, resulting in each SCE platform seeing only one direction of the flow (either the inbound traffic or the outbound traffic).

This problem is typically solved by connecting the two SCE platforms in cascade mode (or through an MGSCP cluster), thereby making sure that both directions of a flow run through the same SCE platform. However, this is sometimes not feasible, due to the fact that the SCE platforms sharing the split flow are geographically remote (especially common upon peering insertion). In this type of scenario, the asymmetric routing solution enables the SCE platform to handle such traffic, allowing SCA BB to classify traffic based on a single direction and to apply basic reporting and global control features to uni-directional traffic.

Asymmetric Routing and Other Service Control Capabilities

Asymmetric routing can be combined with most other Service Control capabilities, however there are some exceptions.

Service Control capabilities that cannot be used in an asymmetric routing topology include the following:

•Subscriber redirect

•Subscriber notification

•Any kind of subscriber integration, including MPLS VPN. (Use subscriber-less mode or anonymous subscriber mode instead)

•Classical open flow mode , including the following:

–Flow-open-mode classical explicitly enabled (ROOT level configuration)

–VAS traffic forwarding mode enabled

–Analysis layer transport mode enabled (ROOT level configuration)

–`no TCP bypass-establishment' mode enabled (ROOT level configuration)

–A traffic rule is configured for certain flows to use the classical open flow mode (ROOT level configuration)

Enabling Asymmetric Routing

The asymmetric routing mode is disabled by default. It is typically enabled by the SCA-BB application when applying an appropriate service configuration.

Note that the detection of uni-directional flows is done by the SCE platform regardless of the asymmetric routing mode, but the appropriate configuration will assure that the uni-directional flows are properly classified and controlled.

For more information, please see the Cisco Service Control Application for Broadband User Guide .

How to Monitor Asymmetric Routing

Use the command below to display the following information regarding asymmetric routing:

•Current status of asymmetric routing mode (enabled or disabled)

•TCP unidirectional flows ratio: the ratio of TCP unidirectional flows to total TCP flows per traffic processor, calculated over the period of time since the SCE platform was last reloaded (or since the counters were last reset).

Step 1 From the SCE>prompt, type show interface linecard 0 asymmetric-routing-topology and press Enter.

Displays the asymmetric routing information.

Monitoring Asymmetric Routing: Example

This example shows how to display the current asymmetric routing information.

SCE>show interface linecard 0 asymmetric routing-topology Asymmetric Routing Topology mode is disabled TCP Unidirectional flows ratio statistics: ========================================== Traffic Processor 1 : 2% Traffic Processor 2 : 7% Traffic Processor 3 : 0% The statistics are updated once every two minutes SCE>

How to Configure a Forced Failure

Use the following commands to force a virtual failure condition, and to exit from the failure condition when performing an application upgrade. (See How to Manage Application Files.)

• How to Force a Virtual Failure

• How to Exit from a Virtual Failure

How to Force a Virtual Failure

Step 1 From the SCE(config if)# prompt, type force failure-condition and press Enter.

Forces a virtual failure condition.

How to Exit from a Virtual Failure

Step 1 From the SCE(config if)# prompt, type no force failure-condition and press Enter.

Exits from the virtual failure condition.

How to Configure the Failure Recovery Mode

The failure-recovery operation-modecommand defines the behavior of the system after boot resulting from failure.

• Options

• Configure the Failure Recovery Mode: Examples

Options

The following options are available:

•operational — after failure, the system will return to operational mode.

•non-operational — after failure, the system will remain not operational.

The default value is operational .

Step 1 From the SCE(config)# prompt, type failure-recovery operation-mode operational|non-operational and press Enter.

Specify the desired failure recovery mode.

Configure the Failure Recovery Mode: Examples

• Example 1

• Example 2

Example 1

This example sets the system to boot as non-operational after a failure.

SCE(config)#failure-recovery operation-mode non-operational
Example 2

This example sets the system to the default failure recovery mode.

SCE(config)# default failure-recovery operation-mode

How to Configure the SCE Platform/SM Connection

• About the SCE Platform/SM Connection

• How to Configure the Behavior of the SCE Platform in Case of Failure of the SM

• How to Configure the SM-SCE Platform Connection Timeout

About the SCE Platform/SM Connection

The user can configure the behavior of the SCE platform in case of failure of the Subscriber Manager (SM):

•If SM functionality is critical to the operation of the system — configure the desired behavior of the SCE platform if any loss of connection with the SM (may be due either to failure of the SM or failure of the connection itself).

•If SM functionality is not critical to the operation of the system — no action needs to be configured.

How to Configure the Behavior of the SCE Platform in Case of Failure of the SM

Options

The following options are available:

•force-failure — Force failure of SCE platform. The SCE platform then acts according to the behavior configured for the failure state.

•remove-mappings — Remove all current subscriber mappings.

•shut — The SCE platform shuts down and quits providing service.

•none (default ) — Take no action.

Step 1 From the SCE(config if)# prompt, type subscriber sm-connection-failure action [force-failure|none|remove-mappings|shut] and press Enter.

Configures the action of the SCE platform in the case of failure of the connection to the SM.

How to Configure the SM-SCE Platform Connection Timeout

You can also configure the timeout interval; the length of time that the SM-SCE platform connection is disrupted before a failed connection is recognized and the configured behavior is applied.

• Options

Options

The following option is available:

•interval — the timeout interval in seconds

Step 1 From the SCE(config if)# prompt, type subscriber sm-connection-failure action timeout intervaland press Enter.

Configures the connection timeout.

How to Enable and Disable Link Failure Reflection

• About Link Failure Reflection

• How to Enable Link Failure Reflection

• How to Disable Link Failure Reflection

• How to Enable and Disable Link Failure Reflection on All Ports

• How to Configure Link Failure Reflection in Linecard-Aware Mode (SCE 2000 only)

About Link Failure Reflection

In some topologies, link failure on one port must be reflected to the related port to allow the higher layer redundancy protocol in the network to detect the failure and function correctly.

The link failure-reflectioncommand determines the behavior of the system when there is a link problem. The link failure-reflection command enables reflection of a link failure. Use the [no] form of this command to disable failure reflection on the link.

The default value is disabled .

How to Enable Link Failure Reflection

Step 1 From the SCE(config if)# prompt, type link failure-reflection and press Enter.

Enables link failure-reflection.

How to Disable Link Failure Reflection

Step 1 From the SCE(config if)# prompt, type no link failure-reflection and press Enter.

Disables link failure-reflection.

How to Enable and Disable Link Failure Reflection on All Ports

• About Link Failure Reflection on All Ports

• Options

• How to Enable Link Failure Reflection on All Ports

• How to Disable Link Failure Reflection on All Ports

About Link Failure Reflection on All Ports

The l ink reflection on all portsfeature extends the link failure reflection feature. It allows the user to determine whether all ports should be taken down if a single port link fails.

In certain topologies, when a failure state occurs on one link, the link state must be reflected to all ports to signal any element using this SCE platform that the device is in a failure state, and therefore cannot be used.

Note The link reflection on all portsfeature cannot be used in a cascade mode, because in this mode one of the links is used to provide redundancy.

In l ink reflection on all portsmode, all ports of the SCE platform are forced down and the link state of the first port is reflected on all the ports.

When recovering from the failure state, the forced down ports (the other link) are brought up only after the first failed port (link) has recovered. In addition, the reflection algorithm will not try to reflect failure for this link again for the next 15 seconds, to avoid link stability problems on auto-negotiation.

Options

The following options are available:

•The on-all-portskeyword enables reflection of a link failure to all ports.

•Use the no form of this command to disable failure reflection to all ports (the on-all-portskeyword is not used in the no form of the command).

The default value is disabled .

How to Enable Link Failure Reflection on All Ports

Step 1 From the SCE(config if)# prompt, type link failure-reflection on-all-ports and press Enter.

Enables failure reflection to all ports.

How to Disable Link Failure Reflection on All Ports

Step 1 From the SCE(config if)# prompt, type no link failure-reflection and press Enter.

Disables failure reflection to all ports.

How to Configure Link Failure Reflection in Linecard-Aware Mode (SCE 2000 only)

• About Link Failure Reflection in Linecard-Aware Mode

• How to Enable Linecard-Aware Mode

• How to Disable Linecard-Aware Mode

About Link Failure Reflection in Linecard-Aware Mode

The linecard-aware-modeoption is an additional extension of the link failure reflection feature for use in MGSCP topologies. Use this option when the subscriber-side interface and the corresponding network-side interface of the same link of the SCE 2000 platform are connected to the same linecard in the router.

This mode reflects a failure of one port to the other three ports of the SCE 2000 differently, depending on different failure conditions, as follows:

•One interface of the SCE 2000 is down: Link failure is reflected to the all other SCE platform ports.

•Two reciprocal ports of the SCE 2000 are down simultaneously, indicating a possible problem in the linecard of the router to which the SCE platform is connected: In this case the failure is not reflected to any of the other interfaces. This allows the second link in the SCE platform to continue functioning without interruption.

Use the no form of this command with the linecard-aware-modekeyword to disable the linecard aware mode without disabling link failure reflection itself.

How to Enable Linecard-Aware Mode

Step 1 From the SCE(config if)# prompt, type link failure-reflection on-all-ports linecard-aware-mode and press Enter.

Enables failure reflection to all ports with linecard aware mode.

How to Disable Linecard-Aware Mode

Step 1 From the SCE(config if)# prompt, type no link failure-reflection linecard-aware-mode and press Enter.

Disables linecard aware mode.

Note that this command does not disable link failure reflection on all ports.