Table of Contents

3.1 Procedures Overview
3.2 Service Provisioning Rules

3.2.1 VCC Configuration Rules
3.2.2 Subtending Considerations

3.3 Creating Logical Pools

3.3.1 Physical Pools Versus Logical Pools
3.3.2 Creating Logical Pools Procedures

3.4 Assigning ATU-C and LIM Ports to a Logical Pool
3.5 Associating Subscriber IDs to LIM Ports

3.5.1 Adding a Subscriber
3.5.2 Adding a Subscriber
3.5.3 Modifying Subscriber Data
3.5.4 Deleting a Subscriber
3.5.5 Setting Subscriber Defaults

3.6 Assigning Subscriber VPI/VCI Addresses

3.6.1 Defining VPI/VCI Addresses
3.6.2 Deleting Subscriber PVCs
3.6.3 Assigning Multiple Destinations

3.7 Unlocking Entities

3.7.1 Unlocking a Module
3.7.2 Unlocking a Port
3.7.3 Unlocking a Subscriber

3.8 Provisioning Subtended Cisco 6100s

Service Provisioning (DOH)

This chapter describes the three Cisco 6100 configuration styles and describes step-by-step instructions for provisioning a Digital Off-Hook (DOH) standard configuration.

Service provisioning is the process for naming subscribers and assigning them to physical and logical pools where they receive ADSL service based on their configuration style. A prerequisite for service provisioning is that a management connection must exist between the Cisco 6100 and the ViewRunner for Windows machine to provision the Cisco 6100. A Cisco 6100 must therefore contain at least a Cisco 6100 multiplexer chassis (MC) and a system controller (SC). During the provisioning process, operator-entered information is sent immediately to the Cisco 6100 via SNMP set and get messages. If the management connection is not communicating properly, lost SNMP messages will retry but eventually will be dropped.

The three primary configuration styles for the Cisco 6100 are:

• DOH Configuration
  In this configuration, MC universal slots are used strictly for ATU-C modules, line concentration chassis (LCCs) are provisioned for line interface modules (LIMs), and POTS splitter chassis (PSC) are provisioned for POTS modules. (Discussed in this section.)

• Direct Connect Configurations
  In a dedicated installation, the POTS splitter modules are wired directly to the ATU-Cs, eliminating the need for LIMs. The system can optionally include one or two redundant ATU-C modules. (Discussed in "Service Provisioning (Direct Connect).")

3.1 Procedures Overview

The general steps for provisioning the Cisco 6100 for the DOH standard configuration style are listed below:

1. Create logical pools.

2. Assign ATU-C and LIM ports to logical pools.

3. Associate subscribers to LIM ports.

4. Assign subscriber VPI/VCI addresses.

5. Unlock entities.

Each of these steps are covered in detail in the following sections. These steps can be executed only after all components have been successfully auto-discovered.

3.2 Service Provisioning Rules

Service provisioning must adhere to a variety of configuration rules which prevent error when establishing ATM connections. ViewRunner for Windows includes service provisioning logic for all valid combinations of configuration data. The configuration rules are discussed in the following subsections.

3.2.1 VCC Configuration Rules

The following are the rules for configuring VCCs.

• A virtual path identifier (VPI) and a virtual circuit identifier (VCI) number combination must be configured for both the subscriber and network sides. You cannot enter VCI numbers alone.

• Subscriber side:

  • Up to four virtual circuit connections (VCCs) per subscriber can be mapped to specific use or general use VPs on the network side.

  • VCCs are addressed on VPI 1 and VCI 1-4.

  • The default setting (for the Cisco 675) is VPI 1 and VCI 1.

  • VCI (0-3) is the valid range for subscriber VCCs on each of the subscriber side VPIs.

  • VPI 1 is defaulted and its modification is prevented through dimming.

• Network side:

  • VCC switching is supported on VPIs 0-27.

  • VPI 0 and 2-27 support 400 VCIs each (VCI 0-399).

  • A warning is issued if VCI 0-31 are used (ATM UNI 3.1 reserves some of these).

  • Virtual path connection (VPC) switching is supported on VPs 28-255.

• Up to 28 VPs are used to support VCC provisioning.

• The remaining 228 VPCs (per ATM UNI 3.1) are reserved for VPC switching in conjunction with subtending.

See the "Cisco 6100 ATM Addressing Guidelines," for more information on configuring VCCs.

3.2.2 Subtending Considerations

Subtending is a Cisco 6100 feature which reduces the cost per subscriber by amortizing the expense of the network interface (NI) module and the edge switch port connection over a large number of subscribers. Subtending is the service and aggregation of data from one or more "downstream" Cisco 6100s to a "host" Cisco 6100 to further oversubscribe the NI. Subtending enables the service provider to amortize an expensive network component (the broadband interface and terminating ATM edge switch port) over a large number of tariffed subscribers.

• Up to six Cisco 6100s can be subtended from a single host Cisco 6100, via dual port 2x DS3 subtend modules and the backplane connector module.

• Subtended VCCs can be switched to the ATM bearer service either through VCCs or VPCs as described in the "Cisco 6100 ATM Addressing Guidelines."

• Standard Cisco 6100 NIs are used on the subtended Cisco 6100s for interconnection to the host node.

The following diagram illustrates the connections of a subtended Cisco 6100 system with six subtended Cisco 6100s:

The following figure shows valid address ranges for each Cisco 6100.

While the valid address space shown above indicates that up to 9600 VCCs can be supported, the number is constrained by several factors. First, as the software content increases with each new release, a greater percentage of existing SC and NI RAM is consumed by resident application code.

For Release 2.x of the Cisco 6100, a maximum of 1500 VCCs within the valid address space is recommended. Software limits are not being built due to the temporary nature of this ceiling.

See the "Cisco 6100 ATM Addressing Guidelines," for more information.

3.3 Creating Logical Pools

A logical pool is a logical grouping of modems and lines. This grouping is used to achieve a particular concentration of subscriber lines to ATU-C modems, such as, 1:1, 2:1, or 6:1. For DOH standard installations, up to three logical pools can be defined per physical pool.

3.3.1 Physical Pools Versus Logical Pools

The MC is divided into two physical pools: A and B. Physical pool A consists of every component in the top half of the chassis and physical pool B is the bottom half. Chassis partitioning into physical pools A and B cannot be changed. The following figure shows the partitioning of the physical pools in the MC.

Each LCC and POTS splitter chassis (PSC) is also divided into physical pools. Physical pool A is the left half of the chassis and Physical Pool B is the right half. Logical pools are constrained to physical pools; that is, a logical pool may only contain lines and modems from modules plugged into a specific physical pool. For more information on physical and logical pools, see the Cisco 6100 Set Up and Installation Manual.

The following figure shows the physical pools for the LCC.

3.3.2 Creating Logical Pools Procedures

To create a logical pool, right click on the MC and select the Pool Properties option.

The Logical Pool - Physical Pool configuration screen appears. This dialog uses two-tiered tabbed property sheets to represent the physical and logical pools. An outer pair of tabs will allow selection of either physical pool A or B. The following example shows the screen with no pools assigned.

To create a logical pool, click the Add Pool Now button. The Logical Pool tab appears:

Within a physical pool tab, a second set of tabs displays depicting the logical pools configured for that physical pool. Logical pool tabs start with logical pool 1 up to logical pool 3.

The dialog displays a variety of statistics describing the configuration of the logical and physical pools. Running totals or summaries of pool assignment describe the characteristics of the ports and subscribers assigned to the pools. Over subscription ratio (OSR), a key statistic in DOH configurations, is calculated using three formulas each of which provide a different view of over subscription. These calculations are kept current for each logical pool. The statistics are initially displayed when the logical pool tab is selected. All statistics are recalculated and updated onscreen whenever you assign or deassign an ATU-C or LIM port from the logical pool.

The following table provides field descriptions for this screen

:

Table 3-1: Physical Pool Fields/Buttons

Field/Button	Description
Logical Pool Name	Logical Pool Name is an optional field that allows a meaningful name to be assigned to the logical pool. The logical pool name may be modified whenever the dialog is open. Note Logical pool naming is not supported in this release
Add Pool Now	Up to three logical pools can be provisioned per physical pool using the Add Pool Now button. Tabs display in the order in which you create them. Therefore, if logical pools 1, 2, and 3 exist and 2 is deleted, then logical pool 3 becomes logical pool 2.
Delete Pool Now	Deassigns any ports that are currently assigned to the logical pool and then deletes the logical pool. Note ViewRunner for Windows requires all assigned LIM ports to be Locked prior to pool deletion. The Delete Pool button is dimmed unless this condition is satisfied.
Over Subscription Ratios Displays the running total of over-subscription within the currently selected logical pool. Three different over subscription formulas are displayed to provide insight into various aspects of the pool characteristics. The ratios that ViewRunner for Windows provides are described below.
Assigned Port OSR	Useful when initially configuring logical pools. This ratio is based on locked entities. Assigned Port OSR effectively displays the target oversubscription provisioning ratio for the pool. Assigned Port OSR equals the number of line ports assigned to the logical pool divided by the number of ATU-C ports assigned to the logical pool.
Provisioned and Unlocked OSR	Useful to verify that the system is properly configured and administratively unlocked to support the target OSR. This ratio will be equal to the assigned port OSR when all provisioning needed to support service is completed and the entities are unlocked. Locking ATU-C ports increases the OSR (for example, 3:1 goes to 6:1). Locking LIMs reduces the OSR (for example, 6:1 goes to 3:1). Provisioned and Unlocked OSR equals the number of unlocked line ports that are: · Assigned to the logical pool · Subordinate to an unlocked module · Associated to an unlocked subscriber This number is then divided by the number of unlocked ATU-C ports assigned to the logical pool that are subordinate to an unlocked module.
Provisioned and In Service OSR	Displays the active OSR that the system is experiencing, factoring required configurations, administrative permissions, and the service state of the pooled ports. This ratio includes the operational state of the system and will vary as alarms set or clear. Provisioned and In Service OSR equals the number of in service line ports assigned to the logical pool that are also associated to an unlocked subscriber. This number is then divided by the number of in service ATU-C ports assigned to the logical pool.
Real-time Display of DOH Service Statistics	Displays running totals of several counts and calculated values. The following statistics are initially displayed when the logical pool tab is selected: The number of line or ATU-C ports assigned within the currently selected logical pool and number of line or ATU-C ports unassigned to any logical pool. The number of provisioned unlocked ports. This is the number of ports within each list box that have the necessary Administrative state configuration to provide service. A properly configured port must be unlocked and subordinate to an unlocked module. Line ports have the additional requirement of being associated to an unlocked subscriber. The number of provisioned and in service ports. The number of ports that have a Service state of In Service and are provisioned properly to provide service. In Service ATU-C ports are implicitly provisioned properly. In Service line ports must also be associated to an unlocked subscriber in order to be provisioned properly to provide service. Running totals are updated whenever a logical pool is deleted, or when a port is assigned or deassigned to or from a logical pool. Providing these statistics in real time is a key value added ViewRunner for Windows feature. These statistics give a summary view of many of the Cisco 6100's critical service parameters and prevents operational mistakes. For large system configurations, most of the list boxes on this dialog will be filled and have scroll bars. These totals provide a convenient summary to replace scrolling the list box and manually tallying DOH service parameters.

Once you select a logical pool, the dialog displays the current configuration of the logical pool. The following rules apply to logical pools:

• ATU-C modem ports have to be locked to be assigned or removed from a logical pool.

• LIM ports must be locked to be assigned or removed from a logical pool.

• Each logical pool may contain zero or more LIM ports and zero or more ATU-C ports. Lines and modems are assigned to pools on a per-port basis, not a per-module basis.

3.4 Assigning ATU-C and LIM Ports to a Logical Pool

In its initial state, auto-discovered resources (LIM and ATU-C ports) are in their respective unassigned windows. Only LIM and ATU-C ports within a physical pool are candidates for assignment into a logical pool belonging to that physical pool.

The list boxes on the bottom third of the screen display unassigned LIM ports and ATU-C modem ports, respectively. The LIM ports are in the left-hand box, the ATU-C modem ports are in the right-hand box.

To assign these to a logical pool, simply drag them using the right mouse button and drop them to the respective list boxes directly above them. ViewRunner for Windows supports multiple drag and drop. To use this feature, select a sequential range of ports by first left clicking on the beginning port and then pressing the Shift key combined with a left click on the last port in the range. To select non-sequential list box ports press the CTRL key simultaneously with left clicking the individual ports to be selected.

Each list box displays the port's Access Identifier (AID), which includes the chassis type and number, slot number, and port number to uniquely identify its location within the Cisco 6100. Additionally, each port's Administrative state, Service state, and its supporting module's Administrative state are displayed. In the case of LIM ports, the associated subscriber's Administrative state is also displayed. That field is blank if no subscriber is configured for the LIM port.

3.5 Associating Subscriber IDs to LIM Ports

Each LIM port must have a subscriber ID associated to it. To add, modify, or delete a subscriber, you will use the LIM Module Properties dialog. Use the following steps to add, modify, or delete a subscriber.

You can add a new subscriber or modify or delete an existing subscriber. If a subscriber is already associated with a port, a Subscriber ID is displayed on both the port and subscriber configuration dialogs.

Step 1 To access the LIM Module Properties dialog, move the cursor down to a LIM module in the Chassis View and right click on the mouse button. The following pop-up menu appears:

Step 2 Highlight the appropriate port properties menu, then select the Configuration option. The LIM Module Properties dialog appears:

The table below provides field descriptions for this screen:
Table 3-2: LIM Module Properties Field

Field/Button	Description
Administrative State	Displays the status of the Administrative state, either Unlocked or Locked. Defaults to Locked.
Subscriber ID	Allows configuration of a unique subscriber record identifier.
Circuit ID	Allows configuration of a unique identifier assigned to this copper local loop circuit.
Physical Pool ID	Displays the physical pool to which this LIM port belongs.
Logical Pool ID	Displays the physical pool to which this LIM port belongs.
Edit Pool	Allows you to edit the logical pool that this LIM port is associated with.
Add Subscriber	Allows you to add a subscriber to this LIM port. Note This button will change to Edit Subscriber if a specific subscriber is being viewed.

3.5.1 Adding a Subscriber

After opening the LIM Module Properties dialog following the previous instructions, execute the following procedures to add a subscriber.

To add a subscriber, click the Add Subscriber button. The Subscriber Properties dialog appears:

3.5.2 Adding a Subscriber

To add a subscriber, use the following procedures:

Step 1 Enter the name of the subscriber in the Subscriber ID field.

Step 2 Select the maximum allowed downstream and upstream rates from the dropdown menu.

Step 3 Enable or disable the 136K Baud feature.

Step 4 Enable or disable the CPE signature feature. (Setting or changing the signature within a 0-127 range).

Step 5 Set or change the timers and their respective values.

Step 6 Click OK or Apply button to save additions.

Step 7 Repeat for every subscriber you want to add.

You can only add subscribers when a subscriber does not exist for the port. This prevents the assignment of more than one subscriber ID per LIM port.

3.5.3 Modifying Subscriber Data

To modify subscriber information, use the following procedures:

Step 1 Enter the name of the subscriber in the Subscriber ID field.

Step 2 Select the maximum allowed downstream and upstream rates from the dropdown menu.

Step 3 Enable or disable the 136K Baud feature.

Step 4 Enable or disable the CPE signature feature. (Setting or changing the signature within a 0-127 range).

Step 5 Set or change the timers and their respective values.

Step 6 Click OK or Apply for the changes to take effect.

3.5.4 Deleting a Subscriber

To delete a subscriber, use the following procedures:

Step 1 Enter the name of the subscriber in the Subscriber ID field.

Step 2 Click on the Delete Now button.

Step 3 Click OK or Apply for the changes to take affect.

The Delete button is dimmed unless the subscriber is locked. If the subscriber's Administrative state has been changed to locked since opening the dialog, and that configuration has not yet been applied, then selecting the Delete button pops up the lock confirmation dialog.

---

Note The subscriber's Service Configuration Group box is dimmed when the subscriber is unlocked.

---

3.5.5 Setting Subscriber Defaults

The user can configure the following subscriber defaults in this release.

• Maximum upstream/downstream trained rates for a subscriber's modem from a list of valid configuration settings using kbps units.

• Upstream and downstream noise margins for a subscriber. The default on installation is 6 upstream and 3 downstream.

• Disconnection timer type for a session or for idle time. The connection time field allows you to determine how many minutes a user may remain idle before disconnection or how many minutes a subscriber's session may run before disconnection.

To access, select Options -> ViewRunner Preferences -> Subscriber Defaults.

3.6 Assigning Subscriber VPI/VCI Addresses

Each subscriber may have multiple permanent virtual circuits (PVCs) provisioned. Each PVC contains both a network side and a subscriber side virtual connection that are known as VCCs. Each VCC has both a VPI and VCI. See "Service Provisioning Rules" for more information on assigning VPI/VCI addresses.

Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be unlocked.

3.6.1 Defining VPI/VCI Addresses

The following procedures explain how to define VPI/VCI addresses for subscribers:

Step 1 Click on the Service Provisioning tab from the Subscriber Properties dialog (see Figure 3-11). The Service Provisioning dialog appears:

You can add or delete a subscriber's PVC in the Service Provisioning dialog, however the subscriber's Administrative state must be locked. Selecting Delete pops up a delete confirmation dialog.

The following table provides field descriptions for this screen

:
Table 3-4: Subscriber Properties - Service Provisioning Fields

Field	Description
Subscriber ID	Displays (read only) the subscriber associated with the PVCs.
Subscriber VPI/VCI	Displays the current subscriber's VPI and VCI.
Network VPI/VCI	Displays the network's VPI and VCI.
Permanent Virtual Connection Group Box	When the subscriber is locked, you can edit the PVC VPI/VCI values and select the Add button to create a new PVC for the subscriber and add it to the PVC connection list, subject to PVC configuration rules. Selecting the Delete button deletes the PVC selected in the PVC connection list. The network and subscriber side VPI/VCI list boxes allow selection of valid VPI and VCI combinations, subject to PVC configuration rules.

Step 2 Enter the VCI/VPI information in their available fields under the Subscribe and
Network group boxes. The subscriber side VPI field is not editable.

Step 3 Click on the Add button.

Step 4 Repeat for every VCI/VPI address you want to add. This takes effect immediately.

Step 5 Click on the Close button when you are finished.

3.6.2 Deleting Subscriber PVCs

To delete subscriber PVCs, use the following procedures:

Step 1 At the Service Provisioning dialog, left-click on the subscriber PVC you want to delete.

Step 2 Click on the Delete button. This takes effect immediately.

Step 3 Repeat for every PVC you want to delete.

Step 4 Click on the Close button when you are finished.

ViewRunner for Windows provides you information regarding valid and invalid VPI and VCI numbers prior to entering a number. ViewRunner for Windows also generates an error dialog when it detects a network side uniqueness violation.

---

Note To add or delete PVC information, the subscriber's Administrative state must be locked.

---

3.6.3 Assigning Multiple Destinations

Once the VPIs and VCIs have been assigned to subscribers, additional VCs can be assigned to a subscriber to provide multiple destinations.

3.7 Unlocking Entities

Once you have entered and verified all logical pool, port, subscriber, and VCI/VPI data, you unlock entities to put them into service. Unlocking simply requires clicking on the Unlocked option in various dialogs and clicking on the Apply button.

Putting a logical pool and provisioned subscriber into service requires unlocking these associated entities:

• ATU-C module

• Appropriate ports on the ATU-C

• LIM module

• Appropriate ports on the LIM

• Provisioned subscriber

3.7.1 Unlocking a Module

To unlock a module, use the following procedures:

Step 1 Right click on the ATU-C module and select the Module Properties >> Configuration option.

The ATU-C Module Properties screen appears:

Step 2 Click on the Unlocked option. This unlocks the module for service.

Step 3 Click Apply and then OK to return to the Chassis view or to unlock a port, click on the Port tab.

Repeat this same procedure on the LIM modules.

3.7.2 Unlocking a Port

To unlock a port, use the following procedures:

Step 1 Right click on an ATU-C module and select the Port Properties >>Configuration option.

The ATU-C Module Properties screen appears:

Step 2 Click on the Unlocked option. This unlocks the port for service.

Step 3 Click Apply and then OK to return to the Chassis view.

Step 4 Repeat this same procedure on the LIM ports.

---

Note Each subscriber must remain locked in order to define PVC information. Once the PVC information is defined, then you can unlock the subscriber.

---

3.7.3 Unlocking a Subscriber

To unlock a subscriber, use the following procedures:

Step 1 Position the cursor on the appropriate LIM port.

Step 2 Right click on the Port Properties >> Configuration option.

Step 3 Click on the Edit Subscriber... button. The Subscriber Properties screen appears:

The LIM Module Properties screen appears:

Step 4 Click on the Unlocked option.

Step 5 Click Apply and then OK to return to the LIM Module Properties window. The subscriber is now unlocked for service.

---

Note If you do not unlock the subscriber, a green blinking LED will appear on the LIM port when the customer premise equipment tries to train for service. If this occurs, the Cisco 6100 will not grant service to the requesting customer.

---

Once you have unlocked a subscriber, you are ready to use the Cisco 6100.

3.8 Provisioning Subtended Cisco 6100s

If you are subtending Cisco 6100s, you provision the local DOH standard subscribers just like you do any Cisco 6100 according to the directions in previous sections. However, you must also provision transit subscribers on the subtended ports of the subtending host Cisco 6100 for each of the subscribers on the subtended Cisco 6100 ports.

The transit subscribers on the host Cisco 6100 must have the same VPI/VCI addresses as assigned to them as they were assigned on the subtended Cisco 6100. For example, if subscriber1 on a subtended Cisco 6100 is assigned VPI 5 and VCI 10, then transit subscriber1 is assigned VPI 5 and VCI 10 on the host Cisco 6100. Because transit subscribers on the host Cisco 6100 are simply logical containers for traffic coming from the subtended Cisco 6100, you can create multiple transit subscribers on one port. However, all VPIs/VCIs must be unique on any one NI, subtended or not, and they must be the same on both ingress and egress. You can define four VCCs per subscriber line coming in from the subtended Cisco 6100.

Subscribers from the subtended node can be assigned across VCCs on the subtending host Cisco 6100. That is, all subscribers from a subtended node can be assigned to VCC 1, or they can be spread across all 32 VCCs. Subscribers can be grouped as desired by the user. For example, if you assign all subscribers from one subtended node to one VCC on the subtending host, you can lock all those subscribers at one time if you need to bring the subtended node down for any reason.

Figure 3-20 shows the Subtend Host Service Provisioning dialog accessed from the subtending host module (MC, slot 9). You will notice that it is similar to the local service provisioning dialogs, but it labels the subscriber side VPI/VCI connection fields as "Transit Subscriber".

You provision the transit subscriber here just as you did that subscriber on the subtended Cisco 6100. See "Associating Subscriber IDs to LIM Ports" for more information.

Posted: Mon Oct 11 22:17:41 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.