|
|
This chapter provides step-by-step instructions for provisioning a Direct Connect configuration.
Service provisioning for Direct Connect is the process of granting asymmetric and symmetric digital subscriber line (ADSL and SDSL) service to subscribers. In a Direct Connect installation, the plain old telephone service (POTS) splitter modules are wired directly to the ADSL transmission unit---central office (ATU-C) or SDSL transmission unit---central office (STU-C), eliminating the need for line interface modules (LIMs). The system can include one or more carrierless amplitude and phase modulation (CAP) ATU-C and STU-C modules.
A prerequisite for service provisioning is that a management connection must exist for ViewRunner for Windows to provision the Cisco 6100 Series system. A Cisco 6100 Series must therefore contain at least a multiplexer chassis (MC) and a system controller (SC) module. During the provisioning process, operator-entered information is sent immediately to the Cisco 6100 Series system by means of Simple Network Management Protocol (SNMP) set and get messages. If the management connection is not working, lost SNMP messages are retried but eventually are dropped.
The three configurations for the Cisco 6100 Series system are
When you provision the Cisco 6100 Series systems for the Direct Connect configuration style, you must use this procedure:
Step 1 Associate each subscriber with a CAP ATU-C, DMT-2 ATU-C or STU-C port
Step 2 Select settings for provisioning
Step 3 Define subscriber VPI/VCI addresses
Step 4 Unlock entities
Each of these steps is covered in detail in the following sections. You can execute these steps only after the successful discovery of all components.
You must adhere to a variety of configuration rules when configuring service for a Cisco 6100
Series Direct Connect system. These rules prevent errors when you are establishing ATM connections. You can read ViewRunner rules regarding combinations of configuration data in the following subsections.
ViewRunner for Windows Release 2.4.0 introduces the use of STU-C modules with the Cisco 6100 Series chassis. Although you can provision STU-C and CAP ATU-C modules similarly, there are differences in provisioning:
1. CAP ATU-C and STU-C modules cannot be inserted in the same chassis at the same time.
2. ViewRunner for Windows does not support the PSD transmit power feature for STU-C modules.
3. Priority Queue cannot be set for STU-C modules.
4. ATM virtual addressing is not supported by STU-C modules for this release.
5. Margin error values cannot be changed for STU-C modules. The fixed upstream margin is 6 dB and the fixed downstream margin is 3 dB.
6. Training rates for the CAP ATU-C module differ from training rates for the STU-C modules. See Section 9.4 for details.
In Direct Connect mode, ViewRunner displays a Port Service Configuration dialog box that shows all of the ports available and those that are in service or capable of service. You can access this dialog box by right-clicking on the Chassis View right side and selecting Port Service Configuration from the drop-down menu. Figure 4-1 shows an example of the Port Service Configuration dialog box.
Logical service-oriented navigation is available from this dialog box, making it easier for you to navigate to a specific port. Click the underlined hyperlink of the port you choose to view.
You must associate a subscriber to each ATU-C and STU-C port. To add, modify, or delete a subscriber, use the ATU-C or STU-C Module Properties dialog box.
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 displays on both the Port and Subscriber Configuration dialog boxes.
Employ the following steps to add, modify, or delete a subscriber:
Step 1 To access the ATU-C or STU-C Module Properties dialog box, move the cursor down to a module and right-click. The menu shown in Figure 4-2 displays.
Step 2 Highlight the Port Properties menu you need and select Configuration. The Module Properties dialog box in Figure 4-3 appears.
Table 4-1 provides field and button descriptions for this dialog box.
:
| Field | Description |
|---|---|
Administrative State | Displays the status of the Administrative state, either Unlocked or Locked. Defaults to Locked. |
Displays the current version of the module's firmware. | |
Subscriber ID | Allows configuration of a unique subscriber record identifier. |
Allows you to edit a subscriber's port configuration. (This button replaces the Add Subscriber button, if you have already assigned a subscriber to this module.) | |
Allows you to add a subscriber to this port. |
After opening the Module Properties dialog box (see Figure 4-3), execute the following procedures to define a subscriber:
Step 1 Click Add/Edit Subscriber.
Step 2 The Subscriber Properties dialog box appears (Figure 4-4 and Figure 4-5).
Step 3 Click Locked in the Administrative state field.
Step 4 Click Apply at the bottom of the dialog box.
Step 5 Enter the appropriate data into the following fields:
Step 6 Click OK.
You can see from comparing Figure 4-4 and Figure 4-5 that the STU-C Max Allowed Downstream/Upstream Rates field shows the same rate for both up and downstream. In addition, the STU-C Margin Configuration and PSD Transmit Power fields are dimmed.
Table 4-2 describes the ATU-C and the STU-C Subscriber Properties dialog box fields. You can read a further discussion of these fields in "Port Provisioning" section.
:
| Field | Description |
|---|---|
Administrative State | Displays the Administrative state of the subscriber. Can be Locked |
Subscriber ID | Subscriber ID is a required ViewRunner for Windows field that must contain 1 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 Subscriber ID is a nonservice-affecting parameter for the Cisco 6100 Series system. 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. See Section 4.4.2 for details about the Circuit ID field. |
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 measured in kbps. In Release 2.4.0, the number of upstream/downstream rate combinations is increased with the addition of support for 136 kilobaud. |
Margin Configuration (Upstream and Downstream) | Allows the operator to associate upstream and downstream margin values with a subscriber. See the "ADSL Training Process" section for more information on setting the margins. Note For ATU-C modules, increasing the margins could prevent a line from training. A warning dialog box appears when you try to change the noise margin. The default margin configuration is 6 dB up and 3 dB down (6 dB down for DMT-2 modules). |
| Note This feature is not available for STU-C modules.
Power spectral density (PSD) sets downstream transmit power in dBm/Hz per-subscriber. Note Cisco advises that you leave the PSD setting at -40 dBm/Hz for ViewRunner for Windows Release 2.4.0. | |
Timer Type | Note This feature is not available for DMT-2 ATU-C or STU-C modules.
Allows you 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 or SDSL 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 module does not support timer settings, all the fields are disabled. Otherwise, the fields are enabled or disabled according to the Administrative state of the subscriber (Locked or Unlocked). The default settings are session timeout at 100 minutes with a valid range of 16 hours. The idle timeout is 0. Disabled timeout has a valid range of 1 to 60 minutes. You can set both timers to force a timeout when the subscriber crosses either threshold. |
| Button | Description |
More Parameters | If the subscriber is using a DMT-2 ATU-C module, this button is active. Click it to open the DMT-2 Subscriber Properties dialog box. See Section 4.5.3 for a description of the More Parameters button on the Subscriber Provisioning dialog box. |
 | Caution Increasing upstream or downstream margins could cause a line not to train. A warning appears when you try to change the noise margin. The default margin configuration for CAP ATU-C and STU-C modules is 6 dB up and 3 dB down. |
You can set subscriber defaults for disconnection timer type for a session or for idle time from the Subscriber Default dialog box. The connection time field allows you to determine how many minutes you can remain idle before disconnection or how many minutes a subscriber's session can run before disconnection.
To access the Subscriber Default dialog box from the toolbar, select Options > ViewRunner Preferences > Subscriber Defaults.
The new Circuit ID field appears on the Subscriber Properties dialog box for ATU-C and
STU-C subscribers.
The inclusion of a circuit ID suffix with the existing subscriber ID provides you with more line and location detail for a particular subscriber.
You can configure and display a circuit ID for each subscriber. The Circuit ID field accepts up to 20 characters. The default value of the Circuit ID field is empty.
Valid characters include
To tune or refine the attenuation of different signals, you can set downstream transmit power in dBm/Hz for each subscriber. Controlled fluctuations in power transmittal can remedy poor
quality transport.
The default value of downstream PSD transmit power attributes is - 40. The unit is dBm/Hz. Upstream ranges are not activated in this ViewRunner for Windows release.
| Caution We advise you to set the transmit power to -40 dBm/Hz in Release 2.4.0 of ViewRunner for Windows. To avoid data transmission errors, do not change the PSD from -40 dBm/Hz. |
ViewRunner for Windows provides provisioning support for DMT-2 ATU-C modules that is consistent with that provided for CAP ATU-C modules.
The addition of DMT-2 ATU-C modules to ViewRunner for Windows allows you to
1. Maximize bit rate while tailoring distribution of information to channel attenuation and noise
2. Adapt to line-changing conditions, including loop and noise
3. Resist channel distortion
The ViewRunner for Windows DMT-2 ATU-C Module Properties dialog box (Figure 4-6) shows a More Parameters button on the Subscriber Properties dialog box. Arrive at this dialog box
using this path: Port > Configuration tab > Edit/Add Subscriber button > Subscriber Properties dialog box.
When selected, the More Parameters button displays additional DMT-2 ATU-C port configuration options. This button is enabled only if the module is type DMT-2 ATU-C.
To configure a DMT-2 ATU-C module
Step 1 Right-click an ATU-C nonsubtended module.
Step 2 Select Port (#) Properties > Configuration.
Step 3 The Module Properties dialog box opens.
Step 4 Click Locked in the Administrative State field.
Step 5 Click Apply at the bottom of the dialog box. The port immediately unlocks and becomes available for configuring.
Step 6 Click Edit Subscriber.
Step 7 The Subscriber Properties dialog box opens (Figure 4-7).
Step 8 Click Locked in the Administrative State field.
Step 9 Click Apply at the bottom of the dialog box.
Step 10 Click More Parameters on the bottom right-hand side of the dialog box.
Step 11 The DMT-2 Subscriber Properties dialog box opens (Figure 4-8).
Each DMT-2 Module dialog box parameter field described below allows you to make error rate adjustments according to various factors such as delay, redundancy, framing and noise.
You can configure the overhead framing structure. However, the DMT-2 does not unilaterally control the overhead framing structure in use.
Overhead framing structure components are
Structure types are defined in Table 4-3.
| Framing Structure | Option Name | Definition |
|---|---|---|
0 | Full overhead framing with asynchronous bit-to-modem timing (enabled synchronization control mechanism) | |
1 | Full overhead framing with synchronous bit-to-modem timing (disabled synchronization control mechanism) | |
2 | Reduced overhead framing with separate fast and sync bytes. Bytes exist in fast and interleaved latency buffer respectively (64 kbit/s framing overhead). | |
3 | Reduced overhead framing with merged fast and sync byte. Bytes exist in either the fast or interleaved latency buffer (32 kbit/s framing overhead). |
You can configure the number of forward error correction (FEC) redundancy bytes in both upstream and downstream margin configuration. The default value is 16.
The options for number of redundancy bytes are as follows:
The upstream and downstream interleaved delays are configurable. The default value is set to 16000 microseconds. See the default Interleaved setting on the Port Provisioning dialog box. See "Port Provisioning" section for details.
The options for delays are as follows:
One default setting is available for the training mode: Standard Train. Training mode is set on the DMT-2 dialog box.
The error message "Reference Source Not Found" displays when modems are incompatible.
With priority queue and latency settings, you can reduce or expand a subscriber's level of service.
To select the priority queue and latency settings for a port, follow this path: Port (#) > Configuration tab > Add/Delete Subscriber button > Subscriber Properties dialog box > Provisioning button > Service Provisioning dialog box (Figure 4-9).
The DMT-2 module priority queue default setting is 3. The priority queue values are
| Caution Passing standard data over queue 1 or queue 2 causes all transmissions except pings to fail. |
To ensure quality of line service, you must configure path latency (delay) for each subscriber permanent virtual circuit (PVC) on each port. The rules listed below apply to path latency configuration:
To set path latency, use this procedure:
Step 1 Go to the DMT-2 dialog box using this path from the 6100 Series chassis: Port (#) > Configuration tab > Edit Subscriber button > Subscriber Properties dialog box > More Parameters button > DMT-2 dialog box (Figure 4-10).
Step 2 Click the drop-down menu next to the Interleaved Delay field and select a value.
Step 3 Click OK.
Step 4 The DMT-2 dialog box closes, showing the still-open Subscriber Properties dialog box.
Step 5 Click Service Provisioning on the Subscriber Properties dialog box.
Step 6 The Service Provisioning dialog box opens.
To change the path latency delay value, use this procedure:
Step 1 Delete all existing path latency in the DMT-2 and Service Provisioning dialog boxes.
Step 2 Add the new path latency following Steps 1 to 3 in the preceding procedure.
Configure priority queue position (line availability options) using the drop-down menu in that field (see Figure 4-11), with 1 representing the lowest delay and highest line availability. Values 1 through 3 represent queues. Queue usage follows these rules:
| Caution
Passing standard data over queue 1 or queue 2 will cause all transmissions except pings to fail. |
To configure priority queue position, use this procedure:
Step 1 Open the Subscriber Properties dialog box for the port you are configuring.
Step 2 Click Service Provisioning.
Step 3 The Service Provisioning dialog box in opens Figure 4-11.
Step 4 Click the drop-down menu in the Queue Priority field, select a value and click Add Now.
The performance monitoring feature supports DMT-2 ATU-C modules only.
The DMT-2 ATU-C module performance displays on the DMT-2 Status dialog box (Figure 4-12) as two column headers, parameter and value. The Parameter column specifies the type of the performance counter. The Value column contains the value of the counter.
To view the most recent performance counter values, open the DMT-2 Status dialog box using
this procedure:
Step 1 Right-click a DMT-2 ATU-C module.
Step 2 Select Port (#) > Status.
Step 3 The CAP ATU-C Module Properties dialog box opens to the port status display.
Step 4 Click More Parameters in the lower left-hand corner of the dialog box.
Step 5 The DMT-2 Status dialog box displays, showing a list of all performance counters and their values as well as Attenuation and SNR Margin values.
Step 6 Click Refresh to retrieve the most recent values.
The Parameter field in the DMT-2 Port Status dialog box has performance counters such as HecVioll and FarCvflfe. These counters measure the DMT-2 ATU-C port performance according to the following factors:
Table 4-4 describes specific performance counter names, equations and definitions.
| Performance Monitor Name | Description |
|---|---|
The near-end HEC_violation_count-I performance parameter is a count of the number of occurrences of a near-end hec-I anomaly. | |
HecViolF | The near-end HEC_violation_count-I performance parameter is a count of the number of occurrences of a near-end hec-F anomaly. |
The near-end HEC_violation_count-I performance parameter is a count of the number of occurrences of a near-end hec-I anomaly. | |
HecCellI | Total_cell_count-I performance parameter is a count of the total number of cells |
Total_cell_count-F performance parameter is a count of the total number of cells passed though the cell delineation process operating on the fast data while in the SYNC state. | |
The far-end attenuation is the attenuation measured at the far-end. It can be read from the eoc ATN register using the eoc command set. The eoc ATN register is coded as an unsigned integer, ranging from 0 to 127, corresponding to a 0 to 63.5 dB attenuation (0.5 dB steps). | |
The far-end SNR margin is the SNR margin measured at the far-end. | |
The SNR margin represents the amount of increased received noise (in dB) relative to the noise power that the system is designed to tolerate and still meet the target bit error rate (BER) of 10 7, accounting for all coding (for example, RS FEC) gains included in the design. The SNR margin ranges from -64.0 dB to +63.5 dB with 0.5 dB steps | |
The attenuation is the difference in dB between the power received at the near-end and that transmitted from the far-end. Received signal power in dBm is the sum of all data-carrying (that is, b i > 0) DMT-2 sub-carrier powers averaged over a 1-second period. Transmitted signal power is 3.65 + 10log(S gi 2) dBm, summed over the data-carrying subcarriers. The attenuation ranges from 0 to 63.5 dB with 0.5 dB steps. | |
This parameter is a count of 1-second intervals for which the ADSL line is unavailable. | |
This parameter is a count of 1-second intervals with one or more CRC-8 anomalies, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects. | |
This parameter is a count of 1-second intervals with one or more ffec anomalies. | |
This parameter is a count of 1-second intervals with one or more fec anomalies. | |
FarEcfLfe | This parameter is a count of interleaved data stream ffec-I anomalies occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
This parameter is a count of fast data stream fec-F anomalies (the number of corrected code words) occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. | |
The near-end User_total_cell_count-I performance parameter is a count of the total number of cells in the interleaved data path delivered at the V-C (for ATU-C) or T-R (for ATU-C) interface. | |
UserCellF | The near-end User_total_cell_count-F performance parameter is a count of the total number of cells in the interleaved data path delivered at the V-C (for ATU-C) or T-R (for ATU-C) interface. |
This parameter is a count of interleaved data stream CRC-8 anomalies occurring during the accumulation period. This parameter is subject to inhibiting.See ANSI T1.231 for inhibiting rules. | |
This parameter is a count of interleaved data stream febe-I anomalies occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. | |
NearCvfL | This parameter is a count of fast data stream CRC-8 anomalies occurring during the accumulation period. This parameter is subject to inhibiting. S ee ANSI T1.231 for inhibiting rules. |
FarCvfLfe | This parameter is a count of fast data stream febe-F anomalies occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
NearEciL | This parameter is a count of interleaved data stream fec-I anomalies (the number of corrected codewords) occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
FarEciLfe | This parameter is a count of interleaved data stream ffec-I anomalies occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
NearEcfL | This parameter is a count of fast data stream fec-F anomalies (the number of corrected codewords) occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
FarEcfLfe
| This parameter is a count of interleaved data stream ffec-I anomalies occurring during the accumulation period. This parameter is subject to inhibiting. See ANSI T1.231 for inhibiting rules. |
NearEcsL | This parameter is a count of 1-second intervals with one or more fec anomalies. |
FarEcsLfe | This parameter is a count of 1-second intervals with one or more ffec anomalies. |
NearEsL | This parameter is a count of 1-second intervals with one or more CRC-8 anomalies, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects. |
NearSesL | This parameter is a count of 1-second intervals with x or more CRC-8 anomalies, or one or more LOS defects, or one or more SEF defects, or one or more LPR defects. The value of x is for further study and might depend upon the data rate. |
NearUasL | This parameter is a count of 1-second intervals for which the ADSL line is unavailable. |
NearSNRMargin | The SNR margin represents the amount of increased received noise (in dB) relative to the noise power that the system is designed to tolerate and still meet the target BER of 10 7, accounting for all coding (for example, RS FEC) gains included in the design. The SNR margin ranges from -64.0 dB to + 63.5 dB (0.5 dB steps). |
FarAttenuation | The far-end attenuation is the attenuation measured at the far-end. It can be read from the eoc ATN register using the eoc command set. The eoc ATN register shall be coded as an unsigned integer, ranging from 0 to 127, corresponding to a 0 to 63.5 dB attenuation (0.5 dB steps). |
The attenuation is the difference (in dB) between the power received at the near-end and that transmitted from the far end. Received signal power in dBm is the sum of all data-carrying (that is, b i > 0) DMT-2 sub-carrier powers averaged over a 1-second period. Transmitted signal power is 3.65+10log(S gi 2) dBm, summed over the data-carrying sub carriers. The attenuation ranges from 0 to 63.5 dB with 0.5 dB steps. | |
The far-end SNR margin is the SNR margin measured at the far-end. It can be read from the eoc SNR register using the eoc command set (see Section 8.1.4). The eoc SNR register is coded as a 2's complement signed integer, ranging from -128 to + 127, corresponding to a -64 to + 63.5 dB SNR margin (0.5 dB steps). |
In a Cisco 6100 Series chassis, when an SC module detects the insertion or extraction of a module, ViewRunner for Windows generates an alarm message.
A new alarm message indicating the addition or deletion of a DMT-2 ATU-C module now exists. View alarm messages from the Options > Current Alarms View menu selection. Read details of DSL disconnect events by clicking the Current Alarms View dialog box links.
To add subscriber information, use the following procedure:
Step 1 Go to the Subscriber Properties dialog box using this path: Port (#) > Configuration tab > Edit Subscriber > Subscriber Properties dialog box.
Step 2 Enter the name of the subscriber in the Subscriber ID field.
Step 3 Select the maximum allowed downstream and upstream rates from the drop-down menu.
Step 4 Click OK or Apply to save additions.
Step 5 Set or change the timers and their respective values.
Step 6 Repeat steps 1 through 5 for every subscriber you wish to add.
You can add subscribers only when a subscriber does not exist for the port. This prevents the assignment of more than one subscriber ID per CAP ATU-C port.
To modify subscriber information, use the following procedure:
Step 1 Go to the Subscriber Properties dialog box using this path: Port (#) > Configuration tab > Edit Subscriber button > Subscriber Properties dialog box.
Step 2 Enter the name of the subscriber in the Subscriber ID field.
Step 3 Select the maximum allowed downstream and upstream rates from the drop-down menu.
Step 4 Enable or disable the 136 kilobaud feature.
Step 5 Enable or disable the CPE signature feature. (Set the signature within a 0 to 127 range.)
Step 6 Set or change the timers and their respective values.
Step 7 Click OK or Apply for the changes to take effect.
To delete a subscriber, use the following procedure:
Step 1 Go to the Subscriber Properties dialog box using this path: Port (#) > Configuration tab > Edit Subscriber button > Subscriber Properties dialog box.
Step 2 Enter the name of the subscriber in the Subscriber ID field.
Step 3 Click Delete Now.
Step 4 Click OK or Apply for the changes to take effect.
The Delete button is dimmed unless the subscriber is locked. If the subscriber's Administrative state has been changed to Locked since the opening of the dialog, and a configuration has not yet been applied, selecting Delete pops up the Lock Confirmation dialog box.
Each subscriber can have multiple permanent virtual circuits (PVCs) provisioned. Each PVC contains both a network side and a subscriber side virtual circuit connection (VCC). Each VCC has both a virtual path ID (VPI) and a virtual circuit ID (VCI). You must associate each defined subscriber to a VPI/VCI address before the subscriber can be unlocked.
ViewRunner for Windows provides virtual connection support for STU-C modules that is consistent with that provided for carrierless amplitude and phase modulation (CAP) ATU-C modules. Except for the training rates, subscriber provisioning for the ATM virtual circuit for STU-C modules is similar to that for the CAP ATU-C module.
The following are the rules for configuring VPCs:
See "Cisco 6100 Series System ATM Addressing Guidelines," for more information on configuring VCCs.
Employ the following procedure to define VPI/VCI addresses for subscribers:
Step 1 Click the Service Provisioning button from the Subscriber Properties dialog box. The Service Provisioning dialog box opens (Figure 4-13 and Figure 4-14).
Step 2 Select the VCI/VPI settings from the available drop-down menus under the Subscriber and Network group boxes.
Step 3 Click Add Now.
Step 4 Repeat for every VCI/VPI address you want to add. This takes effect immediately.
Step 5 Click Close when you are finished.
Table 4-5 provides field descriptions for the fields on the Service Provisioning dialog box
in Figure 4-13.
| Field | Description |
|---|---|
Subscriber ID | Displays (read only) the subscriber associated with the PVCs. |
Displays the current subscriber's VPI and VCI. | |
Network VPI/VCI | Displays the network's VPI and VCI. |
Priority | Priority queue support applies to CAP ATU-C and DMT-2 ATU-C modules. The number 1 represents the lowest delay and highest line availability. The default setting for DMT-2 modules is 3. Values 1 through 3 represent queues. Queue usage generally follows
|
Latency | The default is set to Interleaved delay for this release. See Section 4.5.2 for more information on latency. |
Permanent Virtual Connection Group Box | When the subscriber is locked, you can edit the PVC VPI/VCI values and select Add Now to create a new PVC for the subscriber and add it to the PVC connection list, subject to PVC configuration rules. Selecting Delete 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. |
To delete subscriber PVCs, follow this procedure:
Step 1 At the Service Provisioning dialog box, left-click the subscriber PVC you want to delete.
Step 2 Click Delete. This takes effect immediately.
Step 3 Repeat for each PVC you want to delete.
Step 4 Click Close when you are finished.
ViewRunner for Windows provides you information regarding valid and invalid VPI and VCI numbers before you enter a number. ViewRunner for Windows also generates an error message 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.
The two new fields on the ViewRunner for Windows Service Provisioning dialog box (Figure 4-13 and Figure 4-14), Priority Queue and Path Latency, allow you to present delay and line availability options to the end user when you are employing ATU-C or STU-C modules.
The path latency default setting is Interleaved. Actual interleaved upstream and downstream delay values are configured on the Subscriber Properties DMT-2 dialog box.
Priority queue position is configured on the Service Provisioning dialog box. A drop-down menu in that field displays all available queues, with 1 representing the lowest delay and highest line availability. The ViewRunner for Windows DMT-2 priority queue position is 3. Values 1 through 3 represent queues. Queue usage follows these rules:
| Caution Passing standard data over queue 1 or queue 2 will cause all transmissions to fail except pings. |
Access the Service Provisioning dialog box for CAP ATU-C and DMT-2 ATU-C modules through this path: Port (#) > Configuration tab > Edit Subscriber button > Subscriber Properties dialog box > Service Provisioning button> Service Provisioning dialog box.
The ViewRunner for Windows Release 2.4.0 Subscriber Permanent Virtual Circuits (PVCs) Summary dialog box displays priority queue and latency data per subscriber. You can open this dialog box by right-clicking on the chassis and selecting the View Subscriber PVCs option.
Subtending is a Cisco 6100 Series 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.
You can
Figure 4-15 illustrates the connections of a subtended Cisco 6100 Series system with six
subtended systems.
Figure 4-16 shows valid address ranges for each Cisco 6100 Series system.
Although the valid address space shown in Figure 4-16 indicates that up to 9600 VCCs can be supported, the number is constrained by several factors and so is smaller. A primary factor is the amount of SC module and NI RAM consumed by resident application code.
For Release 2.x of the Cisco 6100 Series system, Cisco recommends a maximum of 1500 VCCs within the valid address space. Software limits might not be built in, due to the temporary nature of this ceiling. See "Cisco 6100 Series System ATM Addressing Guidelines," for
more information.
To subtend Cisco 6100 Series systems, you provision the local subtended subscribers just as you
do any Cisco 6100 Series system according to the directions in "Service Provisioning with a Digital Off-Hook Configuration." The following rules apply to subtending Cisco 6100
Series nodes:
For example,
Figure 4-17 shows the Subtend Host Service Provisioning dialog box, accessed from the subtend host module (MC1, slot9). Notice that the dialog box is similar to the local service provisioning dialog boxes, but the subscriber side VPI/VCI connection fields read "Transit Subscriber."
You provision the transit subscriber on this dialog box just as you did that subscriber on the subtended Cisco 6100 Series system. See the "Associating Subscriber IDs to Ports" section for more information.
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 dialog boxes and clicking Apply.
Putting a provisioned subscriber into service requires unlocking these entities:
To unlock a module, use the following procedure:
Step 1 From the Cisco 6100 Series Chassis View, right-click the ATU-C or STU-C module and select Module Properties > Configuration (Figure 4-18).
This selection opens the Module Properties dialog box for that particular module (Figure 4-19).
Step 2 Click Unlocked on the ATU-C or STU-C Module Properties dialog box. This unlocks the module for service.
Step 3 Click Apply and then OK to return to the Chassis View.
To unlock a port, follow this procedure:
Step 1 From the Cisco 6100 Series Chassis View, right-click an ATU-C or STU-C module and select Port Properties > Configuration (Figure 4-20).
The ATU-C or STU-C Port Properties dialog box appears (Figure 4-21).
Step 2 Click Unlocked. 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 procedure:
Step 1 Position the cursor on the appropriate ATU-C or STU-C port.
Step 2 Right-click Port Properties > Configuration (Figure 4-22).
The ATU-C or STU-C Port Properties dialog box appears (Figure 4-23).
Step 3 Click Add Subscriber. The Subscriber Properties dialog box appears (Figure 4-24).
Step 4 Click Unlocked.
Step 5 Click Apply and then OK to return to the Port Properties dialog box. The subscriber is now unlocked for service.
Once you have unlocked a subscriber, you are ready to use the Cisco 6100 Series system.
Posted: Tue Oct 12 09:34:12 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.