|
Table Of Contents
CLI Commands for Cascaded Systems
Topology-Related Parameters for Redundant Topologies
Configuring the Connection Mode
Installing a Cascaded System
This section outlines the installation procedures for a redundant solution with two cascaded SCE 2000s. For more complete information,refer to the Cisco SCE 2000 4xGBE Installation and Configuration Guide . Refer to the Cisco SCE 2000 4xGBE CLI Command Reference for details of the CLI commands .
When working with two SCE 2000s with split-flow and redundancy, it is extremely important to follow this installation procedure.
To install a cascaded system, complete the following steps:
• Configuring the Connection Mode
Install a Cascaded System
• CLI Commands for Cascaded Systems
• Topology-Related Parameters for Redundant Topologies
CLI Commands for Cascaded Systems
This section presents CLI commands relevant to the configuration and monitoring of a redundant system.
Use the following commands to configure and monitor a redundant system:
connection-mode
[no] force failure-condition
Show interface linecard 'number' connection-mode
Show interface linecard 'number' physically-connected links
Topology-Related Parameters for Redundant Topologies
All four of the topology-related parameters are required when configuring a redundant topology.
•Connection mode — Redundancy is achieved by cascading two SCE platforms. Therefore the connection mode for both SCE platforms may be either:
–Inline-cascade
–Receive-only-cascade
•Physically-connected-links — For each of the cascaded SCE platforms, this parameter defines the number of the link (Link 0 or Link 1) connected to this SCE platform.
•Priority — For each of the cascaded SCE platforms, this parameter defines whether it is the primary or secondary device.
•On-failure — For each of the cascaded SCE platforms, this parameter determines whether the system cuts the traffic or bypasses it when the SCE platform either has failed or is booting.
Step 1 Install both SCE 2000s, power them up, and perform the initial system configuration. (See Connect the Power Supply Units and Connect the Local Console.)
Step 2 Connect both SCE 2000s to the management station.(See Connect the Management Interface )
Step 3 Connect the cascade ports. The cascade ports must be connected directly in Layer 1 (dark fibers), not through switches. (See Information About Cabling.)
Step 4 Set topology configurations for each SCE 2000 via the connection-mode options. (See Topology-Related Parameters for Redundant Topologies and Configuring the Connection Mode.)
Step 5 Make sure that the SCE 2000s have synchronized and active SCE 2000 was selected.
Use the show interface linecard 0 link mode command.
Step 6 If you want to start with bypass/sniffing, change the link mode to your required mode in both SCE 2000s on both links. The bypass mode will be applied only to the active SCE 2000. ( See Link Mode.)
Step 7 Make sure that the link mode is as you required.
Use the show interface linecard 0 link mode command.
Step 8 Connect the traffic port of SCE 2000 #1. This will cause a momentary down time until the network elements from both sides of the SCE 2000 auto-negotiate with it and start working (when working inline). ( See Information About Cabling.)
Step 9 Connect the traffic port of SCE 2000 #2, this will cause a momentary down time until the network elements from both sides of the SCE 2000 auto-negotiate with it and start working (when working inline). ( See Information About Cabling.)
Step 10 When full control is needed, change the link mode on both SCE 2000s on both links to `forwarding'. It is recommended to first configure the active SCE 2000 and then the standby. ( See Link Mode.)
Step 11 You can now start working with the Subscriber Manager.
Configuring the Connection Mode
Use the following command to configure the connection mode, including the following parameters.
•inline/receive only
•physically connected links
•behavior upon failure of the SCE platform
•primary/secondary
To configure the connection mode, use the following command.
Step 1 From the SCE 2000 (config if)# prompt, type connection-mode inline-cascade/receive-only-cascade[physically-connected-links {link-0/link-1}]}] [priority {primary/secondary}] [on-failure {bypass/cutoff}] and press Enter.
Examples
EXAMPLE 1
Use the following command to configure the primary SCE platform in a two-SCE platform inline topology. Link 1 is connected to this SCE platform and the behavior of the SCE platform if a failure occurs is bypass .
SCE 2000(config if)#connection-mode inline-cascade physically-connected-links link-1 priority primary on-failure bypass
EXAMPLE 2
Use the following command to configure the SCE platform that might be cascaded with the SCE platform in Example 1. This SCE platform would have to be the secondary SCE platform, and Link 0 would be connected to this SCE platform, since Link 1 was connected to the primary. The connection mode would be the same as the first, and the behavior of the SCE platform if a failure occurs is also bypass.
SCE 2000(config if)# connection-mode inline-cascade physically-connected-links link-0 priority secondary on-failure bypass
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-mode command 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.)
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-links option).
•Cutoff — completely cuts off flow of traffic through the specified link.
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-links' option to configure the link mode for all links (SCE 2000 platforms only).
•It is recommended that both links be configured together. Use the all-links option.
•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 2000 (config if)# prompt, type
link-mode [<link>>|all-links]. [forwarding|bypass|sniffing|cutoff]
and press Enter.
How to Monitor the System
Use the following commands to view the current connection mode and link mode parameters.
• View Current Connection Mode
View Current Connection Mode
Step 1 From the SCE 2000# prompt, type
show interface linecard 0 connection-mode
and press Enter.View Current Link Mode
Step 1 From the SCE 2000# prompt, type
show interface linecard 0 link mode
and press Enter.View Current Link Mappings
Step 1 From the SCE 2000# prompt, type
show interface linecard 0 physically-connected-links
and press Enter.
Posted: Thu May 31 02:18:40 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.