Guest

Cisco SCE 1000 Series Service Control Engine

Cisco SCE 1000 2xGBE Installation and Configuration Guide, Rel 3.0.5 (HTML)

SCE1000 2xGBE Installation and Configuration Guide


Preface
Document Revision History
Audience
Organization
Related Publications
Conventions
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
1. General Overview
The Cisco Service Control Concept
Service Control for Broadband Service Providers
Cisco Service Control Capabilities
The SCE Platform
Management and Collection
Network Management
Subscriber Management
Service Configuration Management
Data Collection
2. Introduction to the SCE Platform
The SCE Platform
Front Panel
Back Panel
Checking the Shipping Container Contents
SCE 1000 Component List
SCE 1000 Installation Checklist
3. Topology
Issues to Be Considered
SCE Platform Configuration
Failure Detection Mechanism
Bypass Mechanism
Functionality
Physical Installation
Bump-in-the-Wire (Inline) Topology
External Splitting (Receive-only) Topology
Redundancy
Two Platforms on Parallel Links in Bump-in-the-Wire Topology
Failure and Recovery
Physical Installation
Redundancy
Maintaining the Network Links vs Maintaining SCE 1000 Platform Functionality
Topology-Related Parameters
Connection Mode Parameter
On-Failure Mode Parameter
Link Failure Reflection Parameter
Status of the SCE 1000 After Abnormal Boot
4. Installation and Maintenance
Preparing to Install the SCE 1000 Platform
Tools and Parts Required
Site Requirement Guidelines
Installing the SCE 1000 Platform
Installation Precautions
Installing the SCE 1000 on a Workbench or Tabletop
Rack-Mounting a SCE 1000 Platform
Attaching a Chassis Ground Connection
Power Supply Overview
LEDs
Power Supply Specifications
Removing and Replacing a Power Supply Unit
Powering Down the Power Supply Unit and Disconnecting Input Power
Removing the Power Supply Unit
Replacing the Power Supply Unit
Reconnecting the Power
Fan Module Overview
Removing and Replacing the Fan Module
Replacing the Battery
5. Connecting the Management Interfaces and Performing Initial System Configuration
Connecting the Local Console
Setting Up the Local Console
Initial System Configuration
Setup Command Parameters
Step 1: Configuring Initial Settings
Step 2: Configuring the Hostname
Step 3: Setting the Passwords
Step 4: Configuring Time Settings
Step 5: Configuring the DNS Settings
Step 6: Configuring the RDR Formatter Destination
Step 7: Configuring Access Control Lists (ACLs)
Step 8: Configuring SNMP
Step 9: Configuring the Topology-Dependent Parameters
Step 10: Completing and Saving the Configuration
Connecting the Management Interface
Cabling the Management Port
Verifying Management Interface Connectivity
6. Cabling the Line Ports and Completing the Installation
Connecting the line ports to the network
Cabling Diagrams
Configuring the GBE Interface Parameters
Connecting the GBE Line Interface Ports
Testing Connectivity: Examining Link LEDs and Counters
Loading and Activating a Service Control Application
7. Basic SCE 1000 Platform Operations
Starting the SCE 1000 Platform
Checking Conditions Prior to System Startup
Starting the System and Observing Initial Conditions
Final Tests
Managing SCE 1000 Configurations
Viewing Configuration
Saving the Configuration Settings
Recovering a Previous Configuration
Performing Complex Configurations
Rebooting and Shutting Down the SCE Platform
Rebooting the SCE Platform
Shutting Down the SCE Platform
8. Troubleshooting
Troubleshooting Overview
Troubleshooting Tools
CLI Commands for Troubleshooting
The User Log
Check the LEDs
Problem Solving Using a Subsystems Approach
Identifying Startup Problems
Troubleshooting the Power Subsystem
Troubleshooting the Firmware Package Installation
Troubleshooting the Management Subsystem
Troubleshooting the Link Interface Subsystem
A. The External Optical Bypass Module
External Optical Bypass Functionality
The External Optical Bypass Module Front Panel
Installing the External Bypass Module
Installing the Module in a Rack
Cabling the External Optical Bypass Module
Specifications

Preface

This preface describes who should read the SCE 1000 2xGBE Installation and Configuration Guide, how it is organized, and its document conventions.

Document Revision History

Cisco Service Control Release

Part Number

Publication Date

Release 3.0.5

OL-7821-05

November, 2006

Description of Changes

Added maximum hostname length.

Cisco Service Control Release

Part Number

Publication Date

Release 3.0

OL-7821-04

February, 2006

Description of Changes

Updated circuit breaker information.

Cisco Service Control Release

Part Number

Publication Date

Release 3.0

OL-7821-03

December, 2005

Description of Changes

Added the following new features:

  • Redundant management (Mng) port

Cisco Service Control Release

Part Number

Publication Date

Release 2.5.7

OL-7821-02

August, 2005

Description of Changes

Complete reorganization and revision of product documentation.

Audience

This guide is for the networking or computer technician responsible for installing and configuring the SCE 1000 platform on-site. To use this publication, you should be familiar with telecommunications equipment and installation procedures, as well as electronic circuitry and wiring practices. You should also have experience as an electronic or electromechanical technician.

This installation guide explains the initial hardware installation and basic configuration procedures for the SCE 1000. It contains procedures for unpacking and installing the device and performing basic configuration via the setup wizard. After completing the installation and basic configuration procedures covered in this guide, you will then use the appropriate companion publications to more completely configure your system.

This guide contains instructions on how to install and run the SCE 1000 platform. This guide assumes a basic familiarity with telecommunications equipment and installation procedures.

Organization

The major sections of this guide are as follows:

Chapter

Title

Description

Chapter 1

Overview

This chapter provides a brief introduction to Cisco Service Control.

Chapter 2

Introduction to the SCE Platform

This chapter provides a hardware overview of the SCE 1000 platform.

Chapter 3

Topology

This chapter describes the possible deployment topologies of the SCE 1000 and explains how various aspects of the topology determine the configuration of the system.

Chapter 4

Installation and Maintenance

This chapter explains how to install a SCE 1000 platform in a rack or in a general tabletop installation and how to install or replace the power supply units and fan modules.

Chapter 5

Connecting the Management Interfaces and Performing Initial System Configuration

This chapter explains how to connect the SCE 1000 platform to a local console and perform the initial system configuration via the setup wizard that runs automatically.

Chapter 6

Cabling the Line Ports and Completing the Installation

This chapter provides instructions for cabling the Gigabit Ethernet ports for one SCE 1000 topologies and for configuring Gigabit Ethernet (GBE) interface parameters.

Chapter 7

Basic SCE 1000 Platform Operations

This chapter describes how to start up the SCE 1000 platform, reboot, and shutdown. It also describes how to manage configurations.

Chapter 8

Troubleshooting

This chapter provides basic system startup troubleshooting information.

Appendix A

The External Optical Bypass Module

This appendix explains how to install the optional external optical bypass module.

Related Publications

Your SCE 1000 platform and the software running on it contain extensive features and functionality, which are documented in the following resources:

  • Cisco CLI software:

    • Cisco Service Control Engine (SCE) Software Configuration Guide

    • Cisco Service Control Engine (SCE) CLI Command Reference

Note

You can access Cisco software configuration and hardware installation and maintenance documentation on the World Wide Web at Cisco Website URL. Translated documentation is available at the following URL: International Cisco Website

  • For initial installation and startup information, refer to the SCE 1000 2xGBE Quick Start Guide.

  • For international agency compliance, safety, and statutory information for wide-area network (WAN) interfaces for the SCE 1000 platform, refer to the Regulatory Compliance and Safety Information for Cisco Service Control Engine (SCE).

  • For installation and configuration of the other components of the Service Control Management Suite refer to:

    • Cisco SCMS Subscriber Management User Guide

    • Cisco SCMS Collection Manager User Guide

    • Cisco Service Control Application for Broadband User Guide

    • Cisco Service Control Application Reporter User Guide

  • To view Cisco documentation or obtain general information about the documentation, refer to the following sources:

    • Obtaining Documentation

    • The Cisco Information Packet that shipped with your SCE 1000 platform.

Conventions

This document uses the following conventions:

Convention

Description

boldface font

Commands and keywords are in boldface.

italic font

Arguments for which you supply values are in italics.

[ ]

Elements in square brackets are optional.

{x | y | z}

Alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string, or the string will include the quotation marks.

screen font

Terminal sessions and information that the system displays are in screen font.

boldface screen font

Information you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

Nonprinting characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to materials not covered in this manual.

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Warning

Means reader be warned. In this situation, you might do something that could result in bodily injury.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

  • Registered Cisco Direct Customers can order Cisco Product documentation from the networking Products MarketPlace:

    http://www.cisco.com/public/ordsum.html

  • Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

    http://www.cisco.com/pcgi-bin/marketplace/welcome.pl

  • Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at any time, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to http://www.cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website http://www.cisco.com/tac.

P3 and P4 level problems are defined as follows:

  • P3—Your network is degraded. Network functionality is noticeably impaired, but most business operations continue.

  • P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to http://tools.cisco.com/RPF/register/register.do.

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at http://www.cisco.com/tac/caseopen.

Contacting TAC by Telephone

If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

P1 and P2 level problems are defined as follows:

  • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

  • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

Chapter 1. General Overview

This <part> provides a general overview of the Cisco Service Control solution. It introduces the Cisco Service Control concept and the Service Control capabilities. It also briefly describes the hardware capabilities of the Service Control Engine (SCE) platform and the Cisco specific applications that together compose the total Cisco Service Control solution.

The Cisco Service Control Concept

The Cisco Service Control solution is delivered through a combination of purpose-built hardware and specific software solutions that address various service control challenges faced by service providers. The SCE platform is designed to support classification, analysis, and control of Internet/IP traffic.

Service Control enables service providers to create profitable new revenue streams while capitalizing on their existing infrastructure. With the power of Service Control, service providers have the ability to analyze, charge for, and control IP network traffic at multigigabit wire line speeds. The Cisco Service Control solution also gives service providers the tools they need to identify and target high-margin content-based services and to enable their delivery.

As the downturn in the telecommunications industry has shown, IP service providers’ business models need to be reworked to make them profitable. Having spent billions of dollars to build ever larger data links, providers have incurred massive debts and faced rising costs. At the same time, access and bandwidth have become commodities where prices continually fall and profits disappear. Service providers have realized that they must offer value-added services to derive more revenue from the traffic and services running on their networks. However, capturing real profits from IP services requires more than simply running those services over data links; it requires detailed monitoring and precise, real-time control and awareness of services as they are delivered. Cisco provides Service Control solutions that allow the service provider to bridge this gap.

Service Control for Broadband Service Providers

Service providers of any access technology (DSL, cable, mobile, and so on) targeting residential and business consumers must find new ways to get maximum leverage from their existing infrastructure, while differentiating their offerings with enhanced IP services.

The Cisco Service Control Application for Broadband adds a new layer of service intelligence and control to existing networks that can:

  • Report and analyze network traffic at subscriber and aggregate level for capacity planning

  • Provide customer-intuitive tiered application services and guarantee application SLAs

  • Implement different service levels for different types of customers, content, or applications

  • Identify network abusers who are violating the Acceptable Use Policy

  • Identify and manage peer-to-peer, NNTP (news) traffic, and spam abusers

  • Enforce the Acceptable Use Policy (AUP)

  • Integrate Service Control solutions easily with existing network elements and BSS/OSS systems

Cisco Service Control Capabilities

The core of the Cisco Service Control solution is the purpose-built network hardware device: the Service Control Engine (SCE). The core capabilities of the SCE platform, which support a wide range of applications for delivering Service Control solutions, include:

  • Subscriber and application awareness—Application-level drilling into IP traffic for real-time understanding and controlling of usage and content at the granularity of a specific subscriber.

    • Subscriber awareness—The ability to map between IP flows and a specific subscriber in order to maintain the state of each subscriber transmitting traffic through the SCE platform and to enforce the appropriate policy on this subscriber’s traffic.

      Subscriber awareness is achieved either through dedicated integrations with subscriber management repositories, such as a DHCP or a Radius server, or via sniffing of Radius or DHCP traffic.

    • Application awareness—The ability to understand and analyze traffic up to the application protocol layer (Layer 7).

      For application protocols implemented using bundled flows (such as FTP, which is implemented using Control and Data flows), the SCE platform understands the bundling connection between the flows and treats them accordingly.

  • Application-layer, stateful, real-time traffic control—The ability to perform advanced control functions, including granular BW metering and shaping, quota management, and redirection, using application-layer stateful real-time traffic transaction processing. This requires highly adaptive protocol and application-level intelligence.

  • Programmability—The ability to quickly add new protocols and easily adapt to new services and applications in the ever-changing service provider environment. Programmability is achieved using the Cisco Service Modeling Language (SML).

    Programmability allows new services to be deployed quickly and provides an easy upgrade path for network, application, or service growth.

  • Robust and flexible back-office integration—The ability to integrate with existing third-party systems at the Service Provider, including provisioning systems, subscriber repositories, billing systems, and OSS systems. The SCE provides a set of open and well-documented APIs that allows a quick and robust integration process.

  • Scalable high-performance service engines—The ability to perform all these operations at wire speed.

The SCE Platform

The SCE family of programmable network devices is capable of performing application-layer stateful-flow inspection of IP traffic, and controlling that traffic based on configurable rules. The SCE platform is a purpose-built network device that uses ASIC components and RISC processors to go beyond packet counting and delve deeper into the contents of network traffic. Providing programmable, stateful inspection of bidirectional traffic flows and mapping these flows with user ownership, the SCE platforms provide real-time classification of network usage. This information provides the basis of the SCE platform advanced traffic-control and bandwidth-shaping functionality. Where most bandwidth shaper functionality ends, the SCE platform provides more control and shaping options, including:

  • Layer 7 stateful wire-speed packet inspection and classification

  • Robust support for over 600 protocols and applications, including:

    • General—HTTP, HTTPS, FTP, TELNET, NNTP, SMTP, POP3, IMAP, WAP, and others

    • P2P file sharing—FastTrack-KazaA, Gnutella, BitTorrent, Winny, Hotline, eDonkey, DirectConnect, Piolet, and others

    • P2P VoIP—Skype, Skinny, DingoTel, and others

    • Streaming and Multimedia—RTSP, SIP, HTTP streaming, RTP/RTCP, and others

  • Programmable system core for flexible reporting and bandwidth control

  • Transparent network and BSS/OSS integration into existing networks

  • Subscriber awareness that relates traffic and usage to specific customers

The following diagram illustrates a common deployment of an SCE platform in a network.

Figure 1.1. SCE Platform in the Network

SCE Platform in the Network

Management and Collection

The Cisco Service Control solution includes a complete management infrastructure that provides the following management components to manage all aspects of the solution:

  • Network management

  • Subscriber management

  • Service Control management

These management interfaces are designed to comply with common management standards and to integrate easily with existing OSS infrastructure.

Figure 1.2. Service Control Management Infrastructure

Service Control Management Infrastructure

Network Management

Cisco provides complete network FCAPS (Fault, Configuration, Accounting, Performance, Security) Management.

Two interfaces are provided for network management:

  • Command-line interface (CLI)—Accessible through the Console port or through a Telnet connection, the CLI is used for configuration and security functions.

  • SNMP—Provides fault management (via SNMP traps) and performance monitoring functionality.

Subscriber Management

Where the Cisco Service Control Application for Broadband (SCA BB) enforces different policies on different subscribers and tracks usage on an individual subscriber basis, the Cisco Service Control Management Suite (SCMS) Subscriber Manager (SM) may be used as middleware software for bridging between the OSS and the SCE platforms. Subscriber information is stored in the SM database and can be distributed between multiple platforms according to actual subscriber placement.

The SM provides subscriber awareness by mapping network IDs to subscriber IDs. It can obtain subscriber information using dedicated integration modules that integrate with AAA devices, such as Radius or DHCP servers.

Subscriber information may be obtained in one of two ways:

  • Push Mode—The SM pushes subscriber information to the SCE platform automatically upon logon of a subscriber.

  • Pull Mode—The SM sends subscriber information to the SCE platform in response to a query from the SCE platform.

Service Configuration Management

Service configuration management is the ability to configure the general service definitions of a service control application. A service configuration file containing settings for traffic classification, accounting and reporting, and control is created and applied to an SCE platform. SCA BB provides tools to automate the distribution of these configuration files to SCE platforms. This simple, standards-based approach makes it easy to manage multiple devices in a large network.

Service Control provides an easy-to-use GUI to edit and create these files and a complete set of APIs to automate their creation.

Data Collection

The Cisco Service Control solution generates usage data and statistics from the SCE platform and forwards them as Raw Data Records (RDRs), using a simple TCP-based protocol (RDR-Protocol). The Cisco Service Control Management Suite (SCMS) Collection Manager (CM) software implements the collection system, listening in on RDRs from one or more SCE platforms and processing them on the local machine. The data is then stored for analysis and reporting functions, and for the collection and presentation of data to additional OSS systems such as billing.

Chapter 2. Introduction to the SCE Platform

This chapter provides an introduction to the SCE 1000 2xGBE Platform, the Service Control hardware component.

The SCE Platform

The Service Control Engine (SCE) platform, which is the hardware component of the Cisco Service Control solution, is designed to support observation, analysis, and control of Internet/IP traffic. The following table summarizes model information for the SCE 1000 platform

Table 2.1. SCE Platform Model Information

Model number

SCE 1010 2xGBE

Link Type

Gigabit Ethernet

Number of Ports

2

Number of Links

1


Front Panel

The SCE 1000 Front Panel consists of ports and LEDs as shown in the following figures and tables.

Figure 2.1. SCE Platform Front Panel

SCE Platform Front Panel

Table 2.2. SCE 1000 Ports

Port

Quantity

Description

Connect This Port To…

Mng1/ Mng2

2

10/100/1000 Ethernet RJ-45 ports for management of the SCE 1000.

CLI designation: interface Management 0/1, 0/2.

A LAN using an FE cable with an RJ-45 connector.

If both interfaces are used to provide a redundant management interface, connect both ports to the LAN via a switch.

Console

1

RS-232 RJ-45 port for use by technicians

A local terminal (console) using an RS-232 cable with an RJ-45 connector, as provided in the SCE 1000 kit.

AUX

1

RS-232 RJ-45 port used by technicians

 

GBE ports 1 and 2

2

GigabitEthernet ports for connecting to the link.

CLI designation: interface GigabitEthernet 0/1 and 0/2

Refer to Connecting the Line Ports for cabling diagrams for various topologies


Table 2.3. SCE 1000 LED Groups

LED Groups

Description

Power A

  • Continuous green — Power supply A is functioning normally

  • Red — Power supply A present, but malfunctioning

  • Unlit — Power supply A is either not present or has failed.

Power B

  • Continuous green — Power supply B is functioning normally

  • Red — Power supply B present, but malfunctioning

  • Unlit — Power supply B is either not present or has failed.

Status

The Status LED indicates the operational status of the SCE 1000 system, as follows:

  • Unlit — indicates no power from either power unit.

  • Orange — indicates that the system is booting up.

  • Flashing green — indicates that the system is fully operational.

  • Flashing orange — indicates that the system is operational, but is in a warning state.

  • Red — indicates that there is a problem or failure

Note that Alarms are hierarchical: Failure takes precedence over Warning, which takes precedence over operational.

Bypass

  • Continuous green — indicates that the traffic bypasses the SCE 1000 through an internal electrical bypass module.

    Single SCE 1000 topology — The SCE 1000 is either in bypass or sniffing mode

    Cascaded topology — Either the SCE 1000 is forwarding traffic to the other SCE 1000, where it is being processed, or is simply in bypass mode, so traffic through it is not being processed.

  • Unlit — traffic is not being bypassed

    Single SCE 1000 topology — indicates normal operation of the SCE 1000

    Cascaded topology — indicates normal operation of the active SCE 1000

GBE ports

The GBE LEDs indicate the operational status of the SCE 1000 line ports, as follows:

  • Link

    Green — indicates that the port link is up

    Unlit — indicates that the port link is down

  • Rx

    Flashing Green — indicates that there are incoming packets

  • Tx

    Flashing Green — indicates that there are outgoing packets

Mng

The Mng port LEDs indicate the operational status of the SCE 1000 out-of-band LAN-based management port, as follows:

  • Link/Active

    Green — indicates that the port link is up

    Unlit — indicates that the port link is down

  • 10/100/1000

    Green — indicates that the port is set to 100 Mbps

    Unlit — indicates that the port is set to 10 Mbps

    Orange — indicates that the port is set to 1000 Mbps


Back Panel

The SCE 1000 platform back-panel contains the following components:

  • Two field-replaceable power supply units with ON/OFF switches

  • One field-replaceable fan drawer

  • Ground connections

  • One connector to the external bypass module

The rear panels of both the AC- and DC-powered SCE 1000 platforms are shown in the following pair of figures.

Figure 2.2. SCE Platform Back Panel: AC Power

SCE Platform Back Panel: AC Power

Figure 2.3. SCE Platform Back Panel: DC power

SCE Platform Back Panel: DC power

Checking the Shipping Container Contents

Use the SCE 1000 Component List to check the contents of the SCE 1000 platform shipping container.

Do not discard the shipping container. You need the container if you move or ship the SCE 1000 platform in the future.

SCE 1000 Component List

Table 2.4. SCE 1000 Component List

Component

Description

Received

SCE 1000 platform

SCE 1010 2xGBE platform configured with either AC or DC power supplies.

 

Accessories

The following accessories might arrive in separate shipping containers:

 

  • Rack mount kit

  • Two mounting brackets for 19” rack

  • Six screws (Philips), 8-32 x 3/8” (for attaching the brackets to the SCE 1000 chassis)

  • supporting mounting brackets for 19” rack

  • Two crossrail supports for 19” rack with front and back posts

 

  • Management cables

  • Fast Ethernet cable for connecting to the Management ports

  • RS-232 serial cable (DB-9 to RJ-45) for connecting to a local terminal

 

  • Power cables

Two AC power supply cords,if ordered with AC-input power supply units

 

  • Grounding kit

  • Grounding cable

  • Two Hex nuts (#¼”)

  • Two spring washers (#¼”)

 

  • Documentation

If ordered, SCE 1000 hardware and software documentation set and the Cisco Documentation CD-ROM package*

 

Optional Equipment

Four rubber feet for tabletop installation

 

External Optical Bypass module kit

  • 1 External Optical Bypass module

  • 1 19" rack mounting panel

  • 1 control cable

 


*Titles and quantities of documents will vary. You must order the type and quantity of documentation sets when you order the hardware.

Note

We no longer ship the entire SCE 1000 documentation set automatically with each system. You must specifically order the documentation as part of the sales order. If you ordered documentation and did not receive it, we will ship the documents to you within 24 hours. To order documents, contact a customer service representative.

SCE 1000 Installation Checklist

To assist you with your installation and to provide a historical record of what was done by whom, photocopy the following SCE 1000 Installation Checklist. Indicate when each procedure or verification is completed. When the checklist is completed, place it in your site log along with the other records for your new SCE 1000 platform.

Table 2.5. SCE 1000 Installation Checklist

Task

Verified By

Date

Date SCE 1000 received

 

 

SCE 1000 and all accessories unpacked

 

 

Safety recommendations and guidelines reviewed

 

 

Topology verified: number of SCE 1000 platforms, number of links, and whether inline or receive-only

 

 

Installation Checklist copied

 

 

Site log established and background information entered

 

 

Site power voltages verified

 

 

Site environmental specifications verified

 

 

Required passwords, IP addresses, device names, and so on, needed for initial configuration available (refer to Setup Command Parameters)

 

 

Required tools available

 

 

Network connection equipment available

 

 

SCE 1000 mounted in rack (optional)

 

 

AC/DC power cables connected to AC/DC sources and SCE 1000 platform

 

 

Console port set for 9600 baud, 8 data bits, no parity, and 1 stop bit (9600 8N1)

 

 

ASCII terminal attached to console port

 

 

FE management port is operational

 

 

GBE line ports operational

 

 

Network interface cables and devices connected

 

 

System power turned on

 

 

System boot complete (SYSTEM–UP LED is on)

 

 

Correct hardware configuration displayed after system banner appears

 

 


Chapter 3. Topology

This chapter describes the possible deployment topologies of the SCE 1000. The Cisco SCE solution offers a number of basic topology options that permit the user to tailor the SCE Platform to fit the needs of a particular installation. An understanding of the various issues and options is crucial to designing, deploying, and configuring the topology that best meets the requirements of the individual system.

Issues to Be Considered

There are several issues that must be considered in order to arrive at the optimum configuration of the topology-related parameters:

  • Functionality — Will the system be used solely to monitor traffic flow, with report functionality only, or will it be used for traffic flow control, with enforcement as well as report functionality?

  • Physical installation configuration — Will the SCE Platform be installed as inline? Or will the SCE Platform use an optical splitter?

  • Redundancy — Must the system be designed to guarantee uninterrupted service? If so, there must be a backup SCE Platform to assume operation in case of failure of the primary data link.

  • Link failure and recovery — How should the SCE Platform respond to platform failure and subsequent recovery? Should traffic flow continue even though the unit is not operating, or be halted until the platform is repaired/replaced? Should the unit actually resume operation when it is again operational?

SCE Platform Configuration

There are four topology-related parameters:

  • Connection mode — Can be Inline or Receive-only, depending on the physical installation of the SCE 1000:

    May be configured via either the setup command or the connection-mode command.

  • Bypass mode when the SCE 1000 is not operational (on-failure) — This parameter determines whether the system cuts the traffic or bypasses it when the SCE 1000 has failed.

    May be configured via either the setup command or the connection-mode command.

  • Status after reboot caused by fatal error or abnormal shutdown — This parameter determines whether the SCE 1000 returns to normal operational state after a failure.

    May be configured via either the setup command or the failure-recovery operation-mode command.

  • Link failure reflection — This parameter determines the behavior of the system when there is a link problem. In some topologies it is required that link failure on one port be reflected to the other port, to allow the higher layer redundancy protocol in the network to function correctly.

    May be configured via the link failure-reflection command only.

Failure Detection Mechanism

The SCE 1000 contains various mechanisms to monitor the status and to detect failures. The main mechanisms are:

  • Boot time diagnostics failure. When there is a failure in diagnostics testing at boot time the system will remain in failure status.

  • Watchdog mechanism. There are two types of watchdogs:

    • HW watchdog. A hardware mechanism that detects control entity failure.

    • SW watchdog. A software mechanism that periodically checks for software failures in the SCE 1000. If a failure is detected, an error massage is sent and the SCE 1000 reboots.

  • Run time hardware tests. The system periodically tests the hardware components for error. If a hardware component is malfunctioning, it will be discovered by the system within seconds.

Bypass Mechanism

The SCE 1000 includes a Network Interface Card with a bypass mechanism that is enabled upon SCE 1000 failure. In addition, when connected in-line it can also be enabled in normal operation to simultaneously bypass traffic flow to the other side and direct it internally for analysis. In this case it maintains "receive-only"-like monitoring functions, when control functionality is not required.

The bypass card supports the following four modes:

  • Bypass The bypass mechanism preserves the network link, but traffic is not processed for monitoring or for control.

  • Forwarding This is the normal operational mode, in which the SCE 1000 processes the traffic for monitoring and control purposes.

  • Sniffing The bypass mechanism preserves the network link, while in parallel allowing the SCE 1000 to process the traffic for monitoring only.

  • Cutoff There is no forwarding of traffic, and the physical link is forced down (cutoff functionality at layer 1).

Functionality

The SCE 1000 can serve one of two general functions:

  • Monitoring and Control — The SCE 1000 monitors and controls traffic flow. Decisions are enforced by the SCE 1000 depending on the results of the monitoring functions of the SCE 1000 and the configuration of the Service Control Application for Broadband or Mobile solution.

    In order to perform control functions, the SCE 1000 must be physically installed as an inline installation and the connection mode must be “inline”.

  • Monitoring only — The SCE 1000 monitors traffic flow, but cannot control it.

    Either an inline installation or an optical splitter installation may be used for monitoring only. In the latter case connection mode must be “receive-only”.

Physical Installation

There are two options for the physical installation configuration of the SCE 1000 Platform:

  • Inline installation (provides control functionality).

  • Out-of-line installation utilizing an external optical splitte

The physical installation determines the connection mode that should be configured.

Bump-in-the-Wire (Inline) Topology

Typically, the SCE 1000 is connected on a full duplex line between two devices (Router, BRAS, etc.). When the SCE 1000 is installed as a bump-in-the-wire, it physically resides on the data link between the subscriber side and the network side, and can both receive and transmit traffic.

Figure 3.1. Bump-in-the-Wire Installation

Bump-in-the-Wire Installation

A bump-in-the-wire installation is referred to as inline connection mode.

External Splitting (Receive-only) Topology

In external splitting, an external optical splitter resides physically on the GBE link between the subscriber side and the network side. In this topology, the traffic passes through the external splitter, which splits traffic to the SCE 1000. The external splitter is connected to the SCE 1000 via Rx links only. The SCE 1000, therefore, receives traffic only. It does not transmit.

Figure 3.2. External Splitting Topology

External Splitting Topology

An external splitting installation is referred to as receive-only connection mode.

Note that in an external splitting installation, the SCE 1000 has only traffic monitoring capabilities.

Note

Receive-only topologies can also be implemented using a switch. Such a switch must support SPAN functionality that includes separation between ingress and egress traffic and multiple SPAN-ports destinations.

Redundancy

When a high degree of reliability is desired, a second SCE 1000 Platform should be installed to provide backup operation capabilities. This redundant SCE 1000 guarantees uninterrupted functioning of all SCE 1000 operations.

Note

Redundancy is possible in inline installations only.

A single SCE 1000 platform does not provide redundancy for SCE 1000 control functions. In case of failure of the SCE 1000 unit, the SCE 1000 simply bypasses the traffic; the traffic link is not cut, but no control or monitoring functionality is available.

Two Platforms on Parallel Links in Bump-in-the-Wire Topology

Using two SCE 1000 platforms on parallel links provides redundancy for all SCE 1000 features. In case of failure in the active platform, the backup SCE 1000 unit takes over.

Using redundant SCE 1000 platforms is applicable as an overlay to a customer’s redundant topology, on condition that the entire traffic of a specific subscriber (end station, subnet or VLAN) is flowing through one link only. Both links may be active, providing that the subscriber traffic is mutually exclusive.

This redundancy solution addresses any failure in the SCE 1000 platform itself. It is based on the idea that any fatal hardware or software failure will cause the platform to “cut” the link. A “cut” link will cause the routers/switches on both ends to switch the traffic to the standby link. On the standby link, the traffic is analyzed and policies enforced by the standby SCE 1000, which, after the failure, acts as the active SCE 1000.

Note that when both links are simultaneously independently active and redundant for the other link (as is the case when HSRP with two virtual routers is used), if one link fails, its traffic is directed to the other link. However, the overall supported load in the link that is now carrying all the traffic is only equal to one link, not two.

During setup of this topology, the configuration of the two SCE 1000 platforms is done through multi-box configuration. This ensures that both hold the same configurations and policies. The functional operation of switching from the active to standby, SCE 1000 is contingent upon the fact that the two SCE 1000 platforms are in the same Domain. All configurations performed on this Domain are automatically updated on both SCE Platforms. Both boxes should also be assigned to the same Subscriber Domain. For more information on Domains, see the Cisco SCMS Subscriber Manager User Guide.

The common protocols used for redundancy traffic switching between network elements such as routers and switches in networks are Spanning-Tree in layer2, HSRP in layer3 (usually used in data-centers), and other common routing protocols like OSPF or RIP.

Note

When using routing/switching protocols that perform load balancing as well, the load balancing capabilities should be disabled.

The transition to the backup SCE 1000 platform is transparent. Once the routers/switches detected that traffic has been cut, they start sending traffic through the redundant link. After this occurs, the failed SCE 1000 can be fixed/replaced with no downtime, since the box is effectively disconnected from the network. After fixing/replacing the failed SCE 1000, you must copy the configuration of the current active SCE 1000 to the fixed/replaced SCE 1000.

The backup and restore procedures used for copying policies and Service Configurations from one SCE 1000 to the next are detailed in the Service Control Application Suite for Broadband User Guide.

Failure and Recovery

It is important to decide how the system should behave in case of the failure of the SCE 1000, both during the time that the unit is down and after recovery. This decision is influenced by several factors:

  • Physical installation (connection mode)

  • Redundancy

  • Relative importance of maintaining connectivity vs. the continuity of the value-added services that the SCE 1000 enables.

Physical Installation

In a link connection via an external optical splitter, SCE 1000 failure does not affect traffic flow, which continues through the external optical splitter. When the SCE 1000 detects a failure that requires a recover by reboot, it immediately switches to Cutoff mode, stopping all traffic flow over the link until the SCE 1000 unit is restored to operation.

When operation resumes, the defined operational bypass mode is automatically resumed.

The configuration of a bump-in-the-wire installation depends on the remaining two factors.

Redundancy

Redundancy requires two platforms on parallel links, one active and one standby, in inline topology. When the active SCE 1000 platform detects a failure situation, it will immediately switch to Cutoff mode, causing the routers/switches on both ends to switch the traffic to the standby link and thus activate the standby SCE 1000 platform.

There are two options when the failed SCE 1000 platform is finished reloading:

  • It may either actually resume operation in the defined operational bypass mode, returning to its status as the active SCE 1000 platform.

  • It may remain inactive in the failure bypass mode.

Maintaining the Network Links vs Maintaining SCE 1000 Platform Functionality

When a single SCE 1000 is deployed, the user may decide that in case of a failure, maintaining the network link is more important than providing the SCE 1000 functionality. In this scenario, when the SCE 1000 detects a failure that requires a reboot process for recovering, it immediately switches to Bypass mode, allowing all traffic to bypass the SCE 1000. The SCE 1000 stays in Bypass mode maintaining the network link, albeit without SCE 1000 processing, until the SCE 1000 fully recovers from the failure and is ready to resume normal functioning.

Alternatively, the user may decide that the SCE 1000 functionality is sufficiently crucial to require severing the link if the SCE 1000 platform fails. In this case, when the SCE 1000 detects a failure that requires a reboot process for recovering, it immediately switches to Cutoff mode, stopping all traffic flow. The SCE 1000 stays in Cutoff mode, halting all traffic, until it fully recovers from the failure and is ready to resume normal functioning. In Cutoff the physical interface is blocked, enabling the network device connected to the SCE 1000 to sense that the link is down.

Topology-Related Parameters

Refer to the following sections to determine the correct values for all topology-related parameters before beginning run the initial setup of the SCE 1000.

Connection Mode Parameter

The connection mode parameter refers directly to the physical topology in which the SCE 1000 is installed. Installation is possible in either of the two following modes:

  • Inline — The SCE 1000 resides on the data link between the subscriber side and the network side, thus both receiving and transmitting packets.

  • Receive-only — The SCE 1000 does not reside physically on the data link. Data is forwarded to the SCE 1000 via an external optical splitter. The SCE 1000 itself receives only and does not transmit.

Note

Default value = Inline

The connection mode parameter is determined by the physical deployment of the SCE 1000 as follows:

  • Bump-in-the-wire installation = Inline connection mode.

  • External optical splitter installation = Receive-only connection mode.

On-Failure Mode Parameter

As described in the section The Bypass Mechanism, the bypass card supports four different modes. The following two modes are possible when the SCE 1000 is not operational due to platform failure or boot:

  • Bypass The optical splitter forwards traffic with no intervention of the control application running in the SCE 1000 platform, but monitoring functions continue uninterrupted.

  • Cutoff — There is no forwarding of traffic. The link is forced down, resulting in traffic cutoff at Layer1.

The Forwarding mode enables control of traffic flow and is not compatible with the non-operational status.

In a single SCE 1000 topology, the value of this parameter is determined by whether or not the link can be completely cut when the SCE 1000 fails, or whether traffic flow should continue across the link in spite of platform failure.

  • Cutoff mode is required for the following:

    • Redundant inline topology.

    • Non-redundant inline topology if value-added services are crucial and are more important than maintaining connectivity.

  • Bypass mode is required for the following:

    • Non-redundant inline topology if connectivity is crucial.

Link Failure Reflection Parameter

The link failure reflection refers to the behavior of the SCE 1000 when one of the data links fails. Some network redundant topologies require a layer 1 cutoff in order for the network element to recognize the link failure and translate it into action (switch to redundant link). In this case, if one of the ports fails, it must be reflected to the other port as well.

  • Link failure-reflection When one data port link fails, the SCE 1000 forces the other port link down as well. The port will be forced down as long as the first port link is down. When the problematic port link goes up, the other port link will also be turned on again.

  • No link failure-reflection — Link failure is not reflected to the other port.

Note

Default value = no link failure-reflection

Status of the SCE 1000 After Abnormal Boot

This parameter determines whether the SCE 1000 returns to normal operational state after a reboot caused by fatal error or abnormal shutdown. In general, it is desirable that the SCE 1000 resume operation, and as promptly as possible. However, in a redundant topology, a recovered SCE 1000 may remain non-operational. In this case the platform that had been the backup and is currently active will remain active.

The two options for this parameter are:

  • Operational — The status of the SCE 1000 after abnormal boot is operational. The platform automatically resumes functioning in the defined operational link bypass mode.

  • Not Operational — The status of the SCE 1000 after abnormal boot is not operational. The platform remains in the defined failure link bypass mode.

    This option is to be used only in a redundant topology where a second, operational platform exists.

Note

Default value =Operational for all non-redundant systems.

Must be explicitly configured for redundant topologies.

Table 3.1. Topology Configuration Summary Table

Description

Connection mode

On-failure link bypass mode

Admin status after abnormal boot

Link connection via external switch with port-mirroring

Receive-only

Bypass

Operational

Bump-in-the-wire

 

 

 

Bump-in-the-wire, monitor and control, not redundant

Inline

Bypass

Operational

Bump-in-the-wire, monitor only, not redundant

Inline

Bypass

Operational

Bump-in-the-wire, monitor and control, redundant

Inline

Cutoff

Operational[1]

Bump-in-the-wire, monitor only, redundant

Inline

Cutoff

Operational[1]


* Italicized values represent automatically applied defaults that are applied based on previously defined parameters. These values can be changed only via specific CLI commands.

[1]: In a redundant topology, it is also possible to configure admin status after abnormal boot to be Not operational. In this case, though, the SCE 1000 would have to be manually reloaded in order to resume full functionality.

Chapter 4. Installation and Maintenance

This chapter explains how to install a SCE 1000 platform in a rack or in a general tabletop or workbench installation. Additionally, this chapter contains instructions for installing or replacing the power supply units and fan modules.

Warning

Before you install, operate, or service the system, read the Regulatory Compliance and Safety Information for the Cisco Service Control Engine. This guide contains important safety information you should know before working with the system.

Preparing to Install the SCE 1000 Platform

Before installing your SCE 1000 platform, you should consider the power and cabling requirements that must be in place at your installation site, the equipment you need to install the platform, and the environmental conditions your installation site must meet to maintain normal operation. This section guides you through the process of preparing for your SCE 1000 platform installation and the installation in a rack. The section contains the following topics:

Figure 4.1. SCE Platform Dimensions

SCE Platform Dimensions

Table 4.1. SCE 1000 Dimensions

Dimension

Measurement

Height

3.47 inches (9.5 cm)

Width

17.4 inches (4.43 cm)

Depth

18 inches (4.6 cm)

Weight

33 lb (15 kg)


Tools and Parts Required

The SCE 1000 chassis is fully assembled at the factory, including the application and software packages. No assembly is required. However, you need the following tools and equipment to install the SCE 1000 chassis and the rack-mount kit (if installing the SCE 1000 platform in a rack), fan modules, and power supplies:

  • Number 1 and 2 Phillips screwdriver

  • 1/4 inch flat-blade screwdriver

  • #¼” Hex Wrench

  • Screws compatible with your rack (for mounting the SCE 1000 to the rack)

  • 12 AWG or 2.5-mm copper installation wire with hex or loop connectors for DC power leads

    Ring terminals must be UL approved and suitable for 12 AWG wire.

  • Level (optional)

  • Tape measure (optional)

  • Appropriate cables to connect the SCE 1000 to the network and console terminal

  • Rack-mounting kit (optional)

  • A new AC-input or DC-input power supply

  • A new fan module

Site Requirement Guidelines

The environmental monitoring functionality in the SCE 1000 protects the system and components from potential damage from over-voltage and over-temperature conditions. To ensure normal operation and to avoid unnecessary maintenance, plan your site configuration and prepare your site before installation. After installation, make sure the site maintains an ambient temperature of 41°F to 104°F (5°C to 40°C) with short term temperatures ranging from 23°F to 131°F (–5°C to 55°C), and keep the area around the SCE 1000 chassis free from dust.

Planning a proper location for the SCE 1000 and the layout of your equipment rack or wiring closet is essential for successful system operation. Equipment placed too close together or inadequately ventilated can cause system over-heating. In addition, chassis panels made inaccessible by poor equipment placement can make system maintenance difficult.

Airflow

Figure 4.2. Airflow Through the SCE Platform

Airflow Through the SCE Platform

When you plan the location and layout of your equipment rack or wiring closet you need to consider how air flows though your system. The SCE 1000 draws cooling air in through the intake vents on the left side of the chassis, moves the air across the internal components, and out through the right side and rear panel of the chassis. The above figure illustrates the airflow through the SCE 1000.

Note

Remember to leave a two inch (5 cm) clearance on both sides of the SCE 1000 and five inches (12.7 cm) at the rear for adequate airflow for the inlet and exhaust vents.

Site Requirements

The following tables contain the site requirement specifications for the SCE 1000.

Table 4.2. SCE 1000 Environmental Requirements

Specification

Acceptable Range

Temperature -

nominal 41°F to 104°F (5°C to 40°C)

Short term temperatures*

23°F to 131°F (-5°C to +55°C)

Relative humidity

5% to 95% (non-condensing)

Heat dissipation

683 BTU/hour


*Short term is defined as not more than 96 consecutive hours, not more than 15 days in one year. 360 hours total in any given year, but no more than 15 occurrences in a one-year period.

Table 4.3. SCE 1000 Approvals Specifications

Approval

Specification

EMC

  • CE Mark

  • EMISSIONS: FCC Part 15 CFR 47 Class A, EN 55022 Class A, CISPR22 Class A, VCCI Class A, AS/NZS CISPR22 Class A

  • Immunity - EN 50082-1 EN 55024, CISPR24 (ESD, RFI, EFT, etc.) (Commercial)

Safety

UL/CSA 60950, IEC60950, EN60950, AS/NZS, 60950, NOM-019,IEC/EN60825-1, -2, 21CFR1040, 73/23/ECC


For more complete information regarding safety and regulatory compliance, refer to the Regulatory Compliance and Safety Information for the Cisco Service Control Engine document.

Warning

The DC-powered SCE 1000 should be installed in a Restricted Access Location only.

Installing the SCE 1000 Platform

The SCE 1000 operates as either a tabletop or a rack-mounted unit. A rack-mounting kit is included with the SCE 1000 when it is shipped from the factory. The kit provides the hardware needed (see SCE 1000 Component List) to mount the SCE 1000 in either of two types of standard 19-inch equipment rack:

  • 19-inch rack with only two posts in the front — Use the supporting brackets included in the kit

  • 19-inch rack with four posts, two in the front and two in the back — Use the crossrail supports included in the kit

If you are not rack-mounting your SCE 1000, place it on a sturdy tabletop or workbench. A rubber feet kit is included for tabletop installations.

This section provides instructions for the physical installation of the SCE 1000 platform, including how to install the SCE 1000 in a rack, how to install the SCE 1000 on a tabletop or workbench, and how to properly ground the SCE 1000 platform. The section contains the following topics:

Installation Precautions

The router should already be in the area where you will install it, and your installation location should already be determined. If not, see Site Requirement Guidelines and the Site Preparation and Safety Guide.

When installing the SCE 1000, please observe the following conditions:

  • Allow at least 2 inches (5 cm) of clearance at its left and right sides for airflow clearance from the inlet and exhaust vents, and that no exhaust air from other equipment is drawn into the SCE 1000. For descriptions and illustrations regarding airflow, see Airflow.

  • Do not place the SCE 1000 on the floor during installation. Dust that accumulates on the floor is drawn into the interior of the SCE 1000 by the cooling fans. Excessive dust inside the SCE 1000 can cause over-temperature conditions and component failures.

  • Allow at least 5 inches (12.7 cm) of clearance at the front and rear of the SCE 1000 for installing and rudimentary maintenance for accessing network cables or equipment.

  • Ensure that the SCE 1000 will receive adequate ventilation. Do not install the SCE 1000 in an enclosed cabinet where ventilation is inadequate!

  • Provide an adequate chassis Ground (earth) connection for the SCE 1000 (see Attaching a Chassis Ground Connection for instructions).

Installing the SCE 1000 on a Workbench or Tabletop

You can install the SCE 1000 platform on any flat surface as long as the surface is large enough for the SCE 1000 (see the table in SCE 1000 Dimensions), and allows for adequate airflow/ventilation around the sides of the SCE 1000, as described in the Installation Precautions. When installing the SCE 1000 on a workbench or tabletop or in a rack, ensure that the surface is clean and in a safe location.

Figure 4.3. Installing the System on a Flat Surface

Installing the System on a Flat Surface

To install a SCE 1000 platform on a workbench or tabletop, complete the following steps:

  1. Remove any debris and dust from the tabletop or workbench, as well as the surrounding area. Also make sure your path between the SCE 1000 platform and its new location is unobstructed.

  2. Place the SCE 1000 platform on the tabletop or workbench.

  3. View the bottom panel by lifting the SCE 1000, placing your hands around the SCE 1000 sides and lifting the SCE 1000 from underneath. To prevent injury, avoid sudden twists or moves.

    There are four marked locations, indicating where to affix the rubber feet (see figure above).

  4. Attach the rubber feet by removing the adhesive strips and affix the rubber feet onto the marked locations (on the bottom panel).

  5. Replace the SCE 1000 platform firmly on the tabletop or workbench.

    Remember to check for proper ventilation. Allow at least 2 inches (5 cm) on each side for proper ventilation and 5 inches (12.7 cm) at the back for ventilation.and power cord clearance.

This completes the general workbench or tabletop installation.

Proceed to section, Attaching a Chassis Ground Connection to continue the installation.

Rack-Mounting a SCE 1000 Platform

You can mount the SCE 1000 platform to a 19” rack. There are two standard types of equipment racks, and the appropriate brackets for each are provided in the enclosed kit.

  • 19” rack with front rack posts — the mounting kit includes two mounting brackets as illustrated below.

  • 19” rack with front and back rack posts — in addition to the mounting brackets illustrated below, the mounting kit includes two crossrail supports that the unit slides onto.

Mounting Brackets for 2-post Rack

Mounting Brackets for 4-post Rack

The SCE 1000 mounts to the two front rack posts with brackets that attach to the front of the SCE 1000 The inside width between the two posts or mounting strips (left and right) must be at least 17.3 inches (44 cm).

Note

Remember to leave a two-inch (5 cm) clearance on both sides of the SCE 1000 and at the rear for adequate airflow for the inlet and exhaust vents.

Because the inlet and exhaust ports (vents) for cooling air are located at both sides of the chassis, respectively, multiple SCE 1000s can be stacked in a rack with no vertical clearance.

Attaching the Brackets to the SCE 1000

Before installing the SCE 1000 in the rack, you must first install an appropriate rack-mount bracket on each side of the front of the SCE 1000, as illustrated in the following figure. See Tools and Parts Required for a listing of the parts and tools required for installing the rack–mount.

To install the rack-mount brackets on the SCE 1000 chassis, complete the following steps:

  1. Align the rack-mount bracket to the side of the SCE 1000. Choose the proper bracket for your installation (2-post rack or 4-post rack) as illustrated in Rack-Mounting a SCE 1000 Platform.

  2. Insert and tighten three screws.

    Figure 4.4. Attaching the Mounting Brackets (4-post)

    Attaching the Mounting Brackets (4-post)

    Figure 4.5. Attaching the Mounting Brackets (2-post)

    Attaching the Mounting Brackets (2-post)

  3. Repeat steps 1 and 2 on the other side of the SCE 1000.

    This completes the steps for attaching the rack-mount brackets to the SCE 1000.

    If mounting the SCE 1000 in a rack with only two posts, skip to Mounting the System to a Rack.

    If mounting the SCE 1000 in a rack with four posts, proceed to the next step to attach the crossrail supports to the rack.

Attaching the Crossrail Supports to the Rack

When mounting in a rack with four posts (front and back) the two crossrail supports are mounted one on each side of the rack. The SCE 1000 then slides into these crossrails, which support the weight of the unit.

Note

Cisco recommends that you allow at least 1 or 2 inches (2.54 or 5.08 cm) of vertical clearance between the SCE 1000 and any equipment directly above and below it.

To install the crossrail supports on a four-post rack (both front and back posts), complete the following steps:

  1. Assemble the two crossrail supports as illustrated below. Use three screws for