Overview of Service Provisioning for a Direct Connect Configuration

This chapter provides an overview of the provisioning process for a Direct Connect configuration.

Introduction

When you provision service for a Direct Connect configuration, you grant asymmetric digital subscriber line (ADSL) and symmetrical digital subscriber line (SDSL) service to subscribers. During the provisioning process, information that you enter on the ViewRunner GUI passes immediately to the Cisco 6100 Series system by means of Simple Network Management Protocol (SNMP) set-and-get messages.

In a Direct Connect installation, you set up subscribers by wiring the plain old telephone service (POTS) splitter modules directly to the ADSL transmission unit---central office (ATU-C) or SDSL transmission unit---central office (STU-C). Using this method eliminates the need for line interface modules (LIMs). The system can include one or more carrierless amplitude and phase modulation (CAP) ATU-C, discrete multi-tone (DMT)-2 ATU-C, and STU-C modules.

Direct Connect Provisioning---Procedures Overview

Provisioning the Cisco 6100 Series system for a Direct Connect configuration includes the procedures that are described in the following chapters:

For an overview of the system processes that occur during the provisioning process, see "System Processes and Performance with a Direct Connect Configuration," and the ViewRunner for Windows User Guide.

Each set of procedures includes all or some of the following elements:

Description of the procedure overview and purpose
Guidelines and rules that you need to be aware of when performing the provisioning tasks
Illustrations of the dialog boxes that you open to set and monitor subscriber data
Tables that list and describe the buttons and fields in each of the dialog boxes that you use for provisioning
Step-by-step instructions to perform the provisioning task

Guidelines for Provisioning a Direct Connect Configuration

Before you provision subscribers using a Direct Connect configuration, review the following guidelines:

A management connection must exist for ViewRunner to provision the Cisco 6100 Series system. A Cisco 6100 Series chassis must contain at least one of the following hardware:

Cisco 6100/6130 backplane
System controller

ViewRunner supports the following modules
in a Direct Connect configuration:
- Dual-port CAP ATU-C
- Dual-port DMT-2 ATU-C
- Quad-port flexi ATU-C (CAP or DMT)
- Quad-port STU-C
You can choose from the following configurations
when you set up a Direct Connect configuration:
- Direct Connect with a POTS splitter---In this configuration, each subscriber is connected directly to a modem. To increase subscribership, you can add additional chassis to your system. This configuration includes the Cisco 6100/6130 chassis. Dual-port CAP ATU-C, dual-port DMT-2 ATU-C, or quad-port flexi ATU-C (configured as CAP or DMT-2) modules are installed in the chassis. This configuration also includes a POTS splitter chassis, either Cisco 6120 or a Siecor POTS splitter, with CAP POTS or DMT POTS modules installed in the chassis.
- Direct Connect without a POTS splitter---In this configuration, each subscriber is directly connected to a modem. To increase subscribership, you can add more chassis to your system. This configuration includes the Cisco 6130 chassis. Dual-port DMT-2 ATU-C, quad-port flexi ATU-C (configured as CAP or DMT-2), or quad-port STU-C modules are installed in the chassis.
You can use only a Cisco 6130 chassis with a Direct Connect configuration that does not have a Cisco 6120.
Chassis architecture mandates that you insert like modules on one side of the chassis and not mix modules types in a chassis area. In other words, you cannot have both ATU-C and STU-C modules in the same side of the Cisco 6100/6130 chassis at the same time. However, you can insert ATU-C modules on one side of the Cisco 6100/6130 chassis and quad-port STU-C modules on the other side, for example.
A quad-port STU-C module lists four port options, and an ATU-C module lists two port options.

See the Cisco 6100 Series with NI-1 User Guide for descriptions of and instructions for setting up these configurations.

Note Before you can begin provisioning a system, ViewRunner must discover the system and its components.

Table of Contents