|
|
This chapter provides step-by-step instructions for provisioning a Direct Connect configuration of the Cisco 6100.
Service provisioning is the process of granting ADSL service to subscribers. In a Direct Connect installation, the POTS splitter modules are wired directly to the ATU-Cs, eliminating the need for line interface modules (LIMs). The system can optionally include one or two redundant ATU-C modules. A prerequisite for service provisioning is that a management connection must exist for ViewRunner for Windows to provision the Cisco 6100. A Cisco 6100 must therefore contain at least a 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 two primary configuration styles for the Cisco 6100 are:
The general steps for provisioning the Cisco 6100 for this configuration style are listed below:
Step 1 Associate subscriber to an ATU-C port.
Step 2 Define subscriber VPI/VCI addresses.
Step 3 Unlock entities.
Each of these steps is covered in detail in the following sections. These steps can only be executed after all components have been successfully auto-discovered.
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.
The following are the rules for configuring VCCs.
See the "Cisco 6100 ATM Addressing Guidelines," for more information on configuring VCCs.
Subtending is a Cisco 6100 feature which reduces the cost per subscriber by amortizing the expense of the network interface module (NI) 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.
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 may not be built in due to the temporary nature of this ceiling. See "Cisco 6100 ATM Addressing Guidelines," for more information.
Each ATU-C port must have a subscriber ID associated to it. To add, modify, or delete a subscriber, you will use the ATU-C 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 ATU-C Module Properties dialog, move the cursor down to a ATU-C module 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 ATU-C Module Properties dialog appears:
The following table provides field descriptions for this screen
:
| Field/Button | Description |
|---|---|
Administrative State | Displays the status of the Administrative state, either Unlocked or Locked. Defaults to Locked. |
Firmware Version | Displays the current version of the ATU-C module's firmware. |
Subscriber ID | Allows configuration of a unique subscriber record identifier. |
Add Subscriber | Allows you to add a subscriber to this ATU-C port. |
After opening the ATU-C 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:
The following table provides field descriptions for this screen
:
| Field/Button | Description |
|---|---|
Administrative State
| Displays the Administrative state of the subscriber. Can be Locked or Unlocked. |
Subscriber ID | Subscriber ID is a required ViewRunner for Windows field that must contain at least one alphanumeric character up to 20 alphanumeric characters. Its uniqueness is not guaranteed by ViewRunner for Windows. ViewRunner for Windows recognizes and displays subscribers created with NULL subscriber IDs, but does not allow modification of subscriber configuration parameters unless an alphanumeric character has been entered. Note If you input more that 20 characters for the Subscriber ID, the system beeps at you starting with the 21st character, which informs you that you are exceeding the field length.Subscriber ID is a non-service affecting parameter to the Cisco 6100. You can modify the Subscriber ID field when the subscriber is unlocked. |
| Subscriber Association to Port Group Box | |
Circuit ID | Allows configuration of an identifier assigned to the local loop. For this release, Circuit ID is not supported and should be dimmed. |
Module AID and Port Number | Displays the module and port associated with this subscriber. |
| Service Configuration Group Box | |
Max Allowed Upstream/Downstream Rate | Limits the maximum trained rate of a subscriber's modem. List boxes allow selection of the valid configuration settings using kbps units. The up and down selections are completely independent of one another. See "System Operation and Performance (DOH)," for more information on training. Note In Release 2.3.5, the number of upstream/downstream payload combinations are increased with the addition of support for 136K baud.The 136K Baud training rates can now be enabled or disabled through a system wide MIB object. If the 136K Baud training rates are disabled, then those selections will be grayed out in ViewRunner and not selectable by the user. |
Margin Configuration (Upstream and Downstream) | Allows the operator to associate an upstream and a downstream margin value with a subscriber. See "Bit Error Rate and Noise Margin" for more information on setting the margins. Note Because increasing the margins could cause a line not to train, a warning dialog will appear when you try to change the noise margin. The default margin configuration is 6 db up and 3 db down. |
Allow 136 Kbaud | CAP modules support 136 KBaud training rates, which can be allowed or disallowed when the feature is supported by the SC software revision and the subscriber is locked. If the SC supports per-subscriber provisionable 136 KBaud or does not support ATUCPARMS, then the "Allow 136 KBaud" toggle on the Cisco 6100 Properties dialog shall be disabled. If the SC supports ATUCPARMS but does not support per-subscriber 136 KBaud then the toggle is enabled. |
CPE Signature | You can configure per-subscriber CPE signature detection for a a ATU-C module through the Subscriber Properties dialog. You can specify of the minimum CPE signature within a range of 0-127. The default is 0 which essentially disables CPE signature detection. If the system controller (SC) revision supports per-subscriber provisionable CPE detection, then the performance dialog displays dashes in the "Non-Timer Failed Trains" column, and the total for that column is disabled. There is also a new column in the subscriber tab of the performance dialog called "CPE Rejects" which totals the number of CPE signatures not detected by design. In addition, the "Allow non-timer CPE trains" toggle on the Cisco 6100 Properties dialog is disabled unless the SC revision supports ATUCPARMS but does not support per-subscriber provisionable CPE |
Timer Type | Allows the user to specify an ADSL disconnect timer for a session or for idle time. If you select Idle for the timer type, you can specify the number of minutes the subscriber can remain idle before the ADSL connection is disconnected. If you select Session for the timer type, you can specify the number of minutes the subscriber can stay connected. If the SC does not support timer settings, then all the fields will be disabled. Otherwise, the fields will be enabled or disabled depending on the administrative state of the subscriber (locked or unlocked). The default settings are Session timeout at 100 minutes with a valid range of 1-240. The idle timeout 0, or disabled with a valid range of 1 to 60 minutes. You can select both timers to force a timeout when the subscriber crosses either threshold. Note Use the CPE detection feature to discover CPE gear that is not capable of performing Idle or Session timeouts. During training, the CPE detection feature determines if the CPE equipment can be timer enabled. If the equipment can be timer enabled, then training continues. If the equipment cannot be timer enabled, ViewRunner generates an alarm. After a short time, training continues, but the options for setting Idle or Session timeouts via ViewRunner are disabled. |
PVC Idle | If you enabled the Idle timer, you can set the PVC Idle time for cells per minute, and the Lockout time can be set for minutes. The default value of the PVC threshold is zero, or disabled. The range for the PVC threshold is 1 to 2147483647 cells per minute. The PVC threshold is used also for low tide monitoring.
|
Lockout Time | If you enabled the Session timer, you can specify the number of minutes a subscriber will be locked out when the session is disconnected after timeout. The default is 1 with a valid range of 1-60. |
To add 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 Click OK or Apply button to save additions.
Step 4 Enable or disable the 136K Baud feature.
Step 5 Enable or disable the CPE signature feature. (Setting or changing the signature within a 0-127 range).
Step 6 Set or change the timers and their respective values.
Step 7 Repeat for every subscriber you wish 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 ATU-C port.
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 place.
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.
The user can configure the following subscriber defaults in this release.
To access, select Options -> ViewRunner Preferences -> Subscriber Defaults.
In Direct Connect mode, ViewRunner will display a Port Service Configuration dialog which shows all the ports available and those that are in service or capable of service. The following figure shows an example of the Port Service Configuration dialog.
Logical service oriented screen navigation is available from this screen to make it easier for you to navigate to a specific port. Click on the underlined hyperlink.
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.
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 4-5). 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:
| 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.
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.
Once the VPIs and VCIs have been assigned to subscribers, additional VCs can be assigned to a subscriber to provide multiple destinations.
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 provisioned subscriber into service requires unlocking these associated entities:
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.
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.
To unlock a subscriber, use the following procedures:
Step 1 Position the cursor on the appropriate ATU-C port.
Step 2 Right click on the Port Properties >> Configuration option.
The ATU-C Module Properties screen appears:
Step 3 Click on the Add Subscriber... button. The Subscriber Properties screen appears:
Step 4 Click on the Unlocked option.
Step 5 Click Apply and then OK to return to the ATU-C Module Properties window. The subscriber is now unlocked for service.
Once you have unlocked a subscriber, you are ready to use the Cisco 6100 system.
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 subtend ports of the host Cisco 6100 for each of the subscribers on the subtended Cisco 6100 ports.
The transit subscribers on the subtending host Cisco 6100 must have the same VPI/VCI addresses as assigned to them as they were assigned on the subtended Cisco 6100 node. For example, if subscriber1 on a subtended node 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 subtending 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 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 node down for any reason.
Figure 4-15 shows the Subtend Host Service Provisioning dialog, accessed from the subtend host module (MC1, slot9). 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 ATU-C Ports" for more information.
Posted: Mon Oct 11 22:18:00 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.