cc/td/doc/product/dsl_prod/vrmgtsw/vr4w/rel30
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

System Processes and Performance with a Digital Off-Hook Configuration

System Processes and Performance with a Digital Off-Hook Configuration

This chapter describes basic system processes and the performance metrics that are captured as a result of these system processes in a Digital Off-Hook configuration. You can better understand how the system is performing if you understand the processes that the Cisco 6100 Series system uses to establish Digital Off-Hook connections. This chapter provides details about network connection concepts and processes, including bit error rate and margin, CAP RADSL upstream and downstream constellation combinations, training parameters and counters, and how to monitor connection activity.

This chapter includes the following sections:

Digital Off-Hook Operation

The following process occurs when a Cisco 6100 Series system initiates a connection request to the customer premises equipment (CPE) product:

The ADSL Connection Process

The Carrierless Amplitude and Phase Modulation (CAP) rate-adaptive DSL (RADSL) transceivers that are used in Cisco ATU-Cs and ATU-Rs can train at several discrete settings within each of three baud rate ranges. Because the upstream and downstream data paths are transmitted in different frequencies, they train independently.

The Cisco CAP RADSL implementation supports several ADSL training options that you can use to control subscriber traffic. The following sections describe the training option processes including bit error rate and noise margin, payload transmission rates, and modification of noise margins.

Bit Error Rate and Noise Margin

Bit error rate and noise margin are primary factors in achieving subscriber-designated parameters. SDSL and ADSL transceivers seek an upstream and downstream data rate that can be maintained as long as the amount of line noise does not cause a bit error rate (BER) in excess of 1 x 10-7. Line noise is a function of reach and disturbers. As reach or noise in the loop increases, upstream and downstream payload rates decrease. Also, the thinner the copper wire, the more susceptible it is to noise. Line noise is not constant, and a certain amount of line noise fluctuation does not significantly affect the trained rates. Line noise fluctuation is known as the noise margin. The noise margin must be supplied to the transceivers when you use the multiband method of training.

Payload Transmission Rates

Payload data represents transmitted information that is useful to the customer, but may also include additional information such as user-requested network management and accounting information. Upstream and downstream payloads transmit in different frequency ranges; therefore, the two payload rates are established independently. Layer 2 protocol data units (PDUs) are encoded into Layer 1 (xDSL) transmission frequencies through baud rates (also known as symbol rates) and constellations. You can set different baud rates to achieve different payload rates.

CAP RADSL transceivers support one baud rate to establish the upstream payload rate (136 kilobaud), and three baud rates to establish the downstream payload rate (340, 680, and 952 kilobaud). These baud rates enable CAP RADSL implementations to support the following rates:

Modifying Noise Margins

You can modify the noise margins for a subscriber line. If you set a new noise margin, a line that was training successfully might not train after you set a new margin. ViewRunner alerts you to use caution when you change the margin.

Cisco recommends that you set the margin for 6 dB upstream and 3 dB downstream to provide optimal performance. The default values for noise margin are 0 upstream and 0 downstream.

As an example, if you train a unit that is provisioned with a 3 dB downstream margin and a 6 dB upstream margin against 24-ISDN near-end cross talk (NEXT) set to the 0 dB reference level (-52.6 dBm), you can increase the noise to -49.6 dBm at the CPE and -46.6 dBm at the CO, and still maintain a bit error rate less than 1 bit in error for each 10 million sent (10-7). Within each baud rate, transceivers use constellations to encode data into a frequency spectrum, and subsequently enable the discrete payload options. This concept is described in the following section, and the constellation combinations are listed in Table 7-1.

CAP RADSL Upstream and Downstream Constellation Combinations

The concept of constellation combinations refers to the way discrete subscriber line chip sets communicate with each other. Different constellations provide different levels of data transmission accuracy.

Valid CAP RADSL constellations include 256 UC, 256, 128, 64, 32, 16, 8, and 8 extended range. The 128, 32, 8, and 8 extended range constellations are not supported with downstream baud rates of 952 and 680. Because of this, some upstream-downstream payload combinations cannot be achieved.

Table 7-1 shows valid upstream and downstream constellation combinations.


Table 7-1: CAP RADSL Upstream and Downstream Constellation Combinations
Upstream
Kilobaud

136

136

136

136

136

136

136

136

Constellation

256UC

256

128

64

32

16

8

8er1

Kilobaud Const Payload

1088

952

816

680

544

408

272

91

952

256UC

7168

X

X

X

X

D o w n s t r e a m

952

256

6272

X

X

X

X

952

64

4480

X

X

X

X

952

16

2688

X

X

X

X

680

256UC

5120

X

X

X

X

680

256

4480

X

X

X

X

680

64

3200

X

X

X

X

680

16

1920

X

X

X

X

340

256UC

2560

X

X

X

X

X

X

X

X

340

256

2240

X

X

X

X

X

X

X

X

340

128

1920

X

X

X

X

X

X

X

X

340

64

1600

X

X

X

X

X

X

X

X

340

32

1280

X

X

X

X

X

X

X

X

340

16

960

X

X

X

X

X

X

X

X

340

8

640

X

X

X

X

X

X

X

X

136

256UC

1024

X

X

X

X

X

X

X

136

256

896

X

X

X

X

X

X

X

136

128

768

X

X

X

X

X

X

X

136

64

640

X

X

X

X

X

X

X

136

32

512

X

X

X

X

X

X

X

136

16

384

X

X

X

X

X

X

X

136

8

256

X

X

X

X

X

X

X

1er = extended range

Two entries In Table 7-1 represent the downstream rate for a payload of 4480 kbps:

The 680 kilobaud rate with a 256 constellation is the Cisco 6100 Series system and Cisco 675 default for achieving a payload rate of 4480 kbps. This rate combination supports a slightly better reach, according to 24 ISDN NEXT disturbers.

Table 7-1 also includes two entries that represent the downstream rate for a payload of 1920 kbps:

The 340 kilobaud with a 128 constellation is the Cisco 6100 Series system and Cisco 675 default for achieving the payload rate of 1920 kbps. This rate combination is compatible with any of the upstream data rate selections. The 680 kilobaud option is limited to the 1088, 952, 680, or 408 kbps upstream payload.

CAP modules support 136-kilobaud training rates, which can be allowed or disallowed when the system controller module software supports this feature and the subscriber is locked.

If the system controller module supports per-subscriber provisionable 136 kilobaud or does not support ATUCPARMS, the Allow 136K Baud checkbox on the 6100 Properties dialog box Configuration tab is disabled. If the system controller module supports ATUCPARMS, but does not support per-subscriber 136 kilobaud, the toggle is enabled.

Table 7-2 lists valid rate combinations for upstream and downstream data.


Table 7-2: Valid Rate Combinations for Upstream and Downstream Data
Upstream Rate (kbps)
Downstream Rate (kbps) 1088 952 816 680 544 408 272 91

7168

X1

X

X

X

6272

X

X

X

X

5120

X

X

X

X

4480

X

X

X

X

3200

X

X

X

X

2688

X

X

X

X

2560

X

X

X

X

X

X

X

X

2240

X

X

X

X

X

X

X

X

1920

X

X

X

X

X

X

X

X

1600

X

X

X

X

X

X

X

X

1280

X

X

X

X

X

X

X

X

1024

X

X

X

X

X

X

X

960

X

X

X

X

X

X

X

X

896

X

X

X

X

X

X

X

768

X

X

X

X

X

X

X

640

X

X

X

X

X

X

X

X

512

X

X

X

X

X

X

X

384

X

X

X

X

X

X

X

256

X

X

X

X

X

X

X

1x = valid, empty cell = invalid

The actual training procedure is a function of transceiver-controlled parameter exchange and algorithms designed by Cisco to place parameters around valid data rate selections from Table 7-2.

Training Process

The following guidelines apply to the training sequence:

This setting means that control of the downstream data rate is relinquished to the CAP ATU-C (the ATU-C controls the upstream data rate setting by default).

By using the preceding guidelines, the CAP ATU-C has complete control over upstream and downstream data rate selection. You can choose valid upstream and downstream data rate combinations on the ViewRunner GUI. ViewRunner communicates these rates to the CAP ATU-C through the following process:


Figure 7-1: Subscriber Properties Dialog Box



Figure 7-2: Module Properties Dialog Box


Note If you modify the ATU-R upstream and downstream data rates from the preset maximum settings, the modem can train independently. Independent training depends on how you set the data rates in ViewRunner.
Note The CO side sets the rates at which the CPE trains. The CPE cannot change this rate.

CAP ATU-C Train Parameters

This section describes receive signal quality, receiver gain, and transmit power, where transmit power applies to noise margins on the Cisco 6100 Series systems. Each of these trained-line attributes displays in ViewRunner on the CAP ATU-C Module Port Properties dialog box Status tab.

You can change the noise margin (upstream and downstream) for each subscriber line. Increasing this margin could prevent a line that trained previously from training after you change the margin value. When you attempt to increase the noise margins, ViewRunner issues an alert that is similar to the following message:

Warning: Increasing noise margin could reduce the reach for a given data rate, or reduce the achievable data rate for a given reach. In some cases, it may prevent the line from training at all. Please consult product documentation for more information.

Figure 7-3 shows the Port Status tab of a CAP ATU-C Module Properties dialog box for a session in progress. The various train parameters are identified in the CAP ATU-C Module Properties dialog box showing the Service State field as In Service.


Figure 7-3: CAP ATU-C Module Properties Dialog Box---In Service


Receive-Signal Quality

The receive-signal quality is a measure of the signal quality for the upstream channel (from the ATU-R, in the case of the Cisco 675). This value is represented in decibels.

Signal Quality Overview

You can use the signal quality value to estimate the BER or signal-to-noise ratio (SNR) margin for the received data. The signal quality value takes into account the total signal-to-interference ratio (SIR), where the interference includes background noise, cross-talk, residual intersymbol interference, residual echo from the neighboring upstream or downstream data, and distortion.

A perspective of observed signal quality is described in the following paragraph. Stating the explicit, valid signal-quality ranges for a given loop reach is not, however, particularly valuable. The number and variety of interferers and wiring (outside-plant and in-home) creates many different scenarios. Therefore, specific data is not always helpful if, for example, you are trying to institute a corrective action by moving a wire pair to a different binder group as a remedy.

For 7 kft loops, a receive-signal quality of 37 to 44 dB is fairly common, with average interference and a 6 dB noise margin setting. For 10 kft loops, a signal quality range of 32 to 35 dB is common. As loop length increases, the signal quality decreases. Long loops (12 to 15 kft) or loops that have bridge taps could have a signal quality in the low 30s of the decibel range. Very long loops (over 15 kft) can train with a signal quality as low as 20 dB at the decibels margin. If you reduce the noise margin to zero, even longer loops can train with a signal quality as low as 12 dB.

Future RADSL Development

One of the benefits of RADSL is that it figures out the values for optimal performance. RADSL helps you configure a device to operate at a specific speed or to dynamically select the highest practical operating speed. The values are presented in Table 7-1 primarily as an indicator that the trained loop is exhibiting expected characteristics, rather than for troubleshooting purposes.

In a subsequent Cisco 6100 Series system and ViewRunner release, layer 1 performance statistics will be added, which will be more valuable from a historical review perspective for loops that are experiencing problems. For a given training session, if RADSL is unable to overcome loop characteristics in a way that even the lowest upstream and downstream data rates are not supportable, these layer 1 attributes will not be displayed.

Signal Quality and Data Rate Interaction

Data rates are a function of signal quality, rather than signal quality being a function of data rates. For a given requested upstream and downstream data rate combination that you choose in ViewRunner, if the transceivers cannot maintain the data rates to a 10-7 BER (with a 6 dB noise margin insertion), the transceivers seek the next lowest data rate combination where the BER can be preserved.

Beginning with Cisco 6100 Series Release 2.2.1, the node supports selectable noise margins. The Cisco 6100 Series supports a hard-coded 3 dB downstream and 6 dB upstream noise margin setting. This setting is valuable if, for example, a subscriber requests 7.168 Mbps x 1.088 Mbps, but the loop quality is not sufficient to hold the BER to less than or equal to 10-7.

In this example, the subscriber's RADSL train could settle to 6.272 Mbps x 1.088 Mbps. Therefore, interference could be causing the downstream channel to have just enough noise to prevent the 7.168 Mbps data rate from being achieved with the 6 dB margin setting. If you reduce to 3 dB the noise margin that the transceivers must take into account for determining the best data rates to lock onto, you might be able to provide the full 7 x 1 service.

Receiver Gain

Receiver gain is a measure of loop attenuation over the entire DSL frequency spectrum. The ATU-C or STU-C module uses an algorithm to boost receiver gain so that attenuation is corrected for proper support of a given receive data rate.

The ATU-C or STU-C module algorithm attempts to keep gain to a minimum to prevent NEXT. However, if loop conditions warrant, the algorithm must boost gain enough to ensure that the required minimum signal level is received.

CAP modules support 136 kilobaud training rates, which you can allow or disallow when the system controller module software revision supports this feature and the subscriber is locked. If the system controller module supports per-subscriber provisionable 136 kilobaud or does not support ATUCPARMS, the Allow 136 K Baud checkbox on the 6100 Properties dialog box Configuration tab is disabled. If the system controller module supports ATUCPARMS, but does not support per-subscriber 136 kilobaud, the toggle is enabled.

Factors that tend to boost receiver gain are associated with loop impairment. The following factors are two primary ones:

Table 7-3 lists documented reach and receiver gains.


Table 7-3: Reach and Receiver Gain
Reach (ft) Receiver Gain (dB)

16

42

14.5

39

11

27

9

21

8.7

19

Transmit Power

Transmit power is a measure of the downstream power spectral density (PSD) mask. T1E1/97-104R2a states that the PSD for the downstream channel should have an upper limit of -40 dBm/Hz in the nominal passband region with no variation exceeding -37 dBm/Hz.

Caution Cisco advises you to set the transmit power to -40 dBm/Hz. To avoid data transmission errors, do not change the PSD from -40 dBm/Hz downstream and -38 dBm/Hz downstream.

Each network provider chooses the maximum transmit power. As power is boosted, you can extend reach for a given data rate. At the same time, however, the boosted signal can disturb other services.

Although not currently displayed on the ViewRunner GUI, T1E1/97-104R2a also specifies that the PSD for the upstream channel must have an upper limit of -38 dBm/Hz nominal with no variation exceeding -35 dBm/Hz.

Beginning with Cisco 6100 Series Release 2.1.1, you can control transmit power. Controlling transmit power is helpful when the network provider wants to boost or reduce the power of a given loop.

The ATU-R transceiver determines its transmit power during the training process as it tries to fulfill the upstream data rate request. The transceiver tries to support the requested data rate at the lowest possible transmit power to minimize the NEXT in the Cisco 6100 Series system.

Understanding Performance Train Counters

The Cisco 6100 Series system has a variety of connection counters, train counters, and threshold counters that capture DOH system performance statistics. The following counter types are available:

Connection counters:

Train counters:

Threshold counters:

Counters display individual subscriber, LIM port, and CAP ATU-C modem port statistics.

If the CAP ATU-C modem and ATU-R modem train, a successful train counter increments for the CAP ATU-C modem. If the CAP ATU-C modem and ATU-R modem fail to train, a failed train counter increments for the CAP ATU-C modem. You can view train counter statistics on the Performance Management dialog box.

Connection Counters

Once you have successfully connected a LIM port and CAP ATU-C modem, a successful connection counter increments for both the logical pool and the line. At that point, the modem training sequence begins.

If all of the modems within the logical pool are busy, the system controller module sends a busy tone to the ATU-R modem and increments the logical pool blocked-connection and line blocked-connection counters.

Train Counters

After the connection between the LIM port and CAP ATU-C modem is established, the training sequence begins.

If the CAP ATU-C modem and ATU-R modem train, a successful train counter increments for the CAP ATU-C modem. If the CAP ATU-C modem and ATU-R modem fail to train, a failed train counter increments for the CAP ATU-C modem.

Threshold Counters

Two threshold counters are available for each logical pool, 80 percent and 100 percent modem usage. These two threshold counters provide the following statistics:

The sum of the these statistics is equal to the total connection requests that the logical pool handles.

Note Counters continue to increment unless you reset the system controller module.

In addition to the integer connection counters, connection activity is also represented in terms of percentage connections in each category.

Getting Performance Management Feedback

You can get feedback from the Performance Management dialog box on the current performance of each logical pool in a DOH system. You can choose a particular physical and logical pool on the dialog box and view the following performance statistics for that selection. These statistics are reflected on the tabs that are described in the following sections:

To access any of these views, right-click the chassis rim and choose 6100 Performance from the Chassis menu. Each tab contains Pool tabs that display the following pool information:

Each Performance Management dialog box has its own set of associated counters. ViewRunner resets these counters under certain conditions. The specific counters and the conditions in which a counter is or is not reset are described in the following sections.

Counters do not reset if you take any of following actions:

Performance Management---Pool Summary Tab

The Pool Summary tab provides detailed information about successful and blocked connections, and successful and failed CAP ATU-C trains (see Figure 7-4). Summary statistics that indicate the number of trains at or below 80 percent logical pool use, over 80 percent, and blocked requests for each logical pool are also provided on this dialog box.


Figure 7-4: Performance Management Dialog Box---Pool Summary Tab


The Cisco 6100 Series system maintains pool summary counters in each defined pool in the Pool Summary tab fields, as described in Table 7-4.


Table 7-4: Pool Summary Fields
Field Description
Digital Off-Hook Connection Statistics

Pool Time

Displays the number of minutes that the logical modem pool has been in existence (or since the last reset).

Block Time

Displays the percentage of time (in minutes) during which one or more subscribers were refused modem port assignments in response to DOH connection requests.

Successful Connections < 80%

Displays the number of successful cross-connections (modem assigned) below the 80 percent threshold.

Successful Connections >80%

Displays the number of successful cross-connections (modem assigned) above the 80 percent threshold.

Blocked Connections

Displays the number of blocked cross-connections (modem unavailable).

Total Connection Requests

Displays the total number of requests for connection.

Number of In Service ATU-C Ports

Displays the number of in-service modem ports.

80% Threshold of In Service ATU-C Ports

Number of successful connections while modems are 80 percent used (modems assigned).

ATU-C Port Training Statistics

Successful Trains

Number of times 100 percent modem use is reached (modems assigned).

Failed Trains

Number of failed trains.

Total Trains Initiated

Sum of successful trains and failed trains.

ATU-C Ports Failing to Train

Number of ATU-C ports that have attempted to train and failed.

Line Ports Connected to ATU-C Ports Failing to Train

Number of line ports that are connected to ATU-C ports, which have attempted to train and failed.

ViewRunner resets the Pool Summary tab counters in the following situations:

Performance Management---Subscriber Tab

The Subscriber tab lists data about all successful and blocked-connection activity by a specific subscriber. In addition, summary statistics indicate the number of connections at, below, or over 80 percent logical pool use. Summary statistics also display blocked requests for each logical pool.

To access the Subscriber tab, place your cursor over the outside edge or rim of the chassis, right-click, and choose 6100 Performance. The Subscriber tab shown in Figure 7-5 opens.


Figure 7-5: Performance Management Dialog Box---Subscriber Tab


Table 7-5 describes the columns on the Subscriber tab. The statistics display at the bottom of the dialog box.


Table 7-5: Performance Management Dialog Box---Subscriber Tab Columns
Column Description

Subscriber ID

The unique identifier by which the subscriber is known.

Successful Xconn

The number of successful cross connections that have been achieved for that subscriber ID since the last time ViewRunner reset the counter.

Blocked Xconn

The number of blocked cross connections that have been realized for that subscriber ID since the last timeViewRunner reset the counter.

Subscriber Statistics

The current counts of the following statistics display at the bottom of the tab:

  • Subscribers

  • Successful connections

  • Blocked connections

The Cisco 6100 Series system maintains the following subscriber counters:

ViewRunner resets Subscriber counters if you take any of the following actions:

Performance Management---Line Ports Tab

The Line Ports tab lists data about all successful and failed CAP ATU-C trains by line port. The Line Ports tab is shown in Figure 7-6.


Figure 7-6: Performance Management Dialog Box---Line Ports Tab


Table 7-6 describes the columns on the Line Ports tab. The statistics display at the bottom of the dialog box.


Table 7-6: Performance Management Dialog Box---Line Port Tab Fields
Column Description

Line Port

The line port location by chassis, slot, and line port number.

Successful Trains

The number of successful trains that have been achieved for that line port since the last time ViewRunner reset the counter.

Failed Trains

The number of failed trains that have been realized for that line port since the last time ViewRunner reset the counter.

Line Statistics

The current counts of the following statistics display at the bottom of the tab:

  • Line ports

  • Successful trains

  • Failed trains

  • Nontimer failed trains

  • Line ports connected to ATU-C ports failing to train

The Cisco 6100 Series system maintains the following statistics for each line port counter:

The Cisco 6100 Series system maintains the following statistics for each line port counters:

ViewRunner resets Subscriber counters if you take any of the following actions:

Performance Management---ATU-C Ports Tab

The ATU-C Ports tab lists data about all successful and failed ATU-C trains by the CAP ATU-C modem port. The ATU-C Ports tab is shown in Figure 7-7.


Figure 7-7: Performance Management Dialog Box---ATU-C Ports Tab


Table 7-7 describes the columns on the ATU-C Ports tab. The statistics display at the bottom of the dialog box.


Table 7-7: Performance Management Dialog Box---ATU-C Ports Tab Fields
Column Description

CAP ATU-C Modem Port

CAP ATU-C modem port location by chassis, slot, and line port number.

Successful Trains

Number of successful trains that have been achieved for that CAP ATU-C modem port since the last time ViewRunner reset the counter.

Failed Trains

Number of failed trains that have been realized for that CAP ATU-C modem port since the last time ViewRunner reset the counter.

The Cisco 6100 Series system maintains the following counters in each CAP ATU-C port:

CAP ATU-C port counters are reset if you take any of the following actions:

Current Connection Activity

ViewRunner includes two methods for displaying the status of current subscriber connections:

Usage State Group Box

For CAP ATU-Cs or LIMs in a pooled Digital Off-Hook configuration, the Status tab on the Module Properties dialog box displays a Usage State group box (Figure 7-8).


Figure 7-8: Module Properties Dialog Box---Usage State Group Box


Fields on the Usage State group box identify the specific LIM and CAP ATU-C ports that are currently interconnected. You can click the LIM Properties button to open the Module Properties tab of the opposing port.

Note These fields are dimmed when the port Usage state is Idle.

Active Connections Dialog Box

The Active Connections dialog box lists data about all currently active connections in the Cisco 6100 Series system. To open the Active Connections dialog box, right-click the chassis GUI and choose Active Connections from the Chassis menu. The Active Connections dialog box, shown in Figure 7-9, Figure 7-10, and Figure 7-11 appears. Because there are several columns on this dialog box, these three figures present the Active Connections dialog box first in the far-left position, then scrolling right for the last two figures.


Figure 7-9: Active Connections Dialog Box---Left Side



Figure 7-10: Active Connections Dialog Box---Center



Figure 7-11: Active Connections Dialog Box---Right Side


Note You can use the logical service-oriented navigation to go directly to the desired entity by clicking on any blue, underlined hyperlink in the dialog box.

Table 7-8 describes the columns in the Active Connections dialog box.


Table 7-8: Active Connections Dialog Box Columns
Column Description

Pool

Lists the names of the physical and logical pools.

Active Connections

Lists the number of active connections that are associated with a physical or logical pool.

In Service Modems

Lists the number of in-service modems that you have assigned to a logical pool and whose modules and ports are unlocked.

% Usage

Displays the percentage that represents the value in the Active Connections column divided by the value in the In Service Modems column.

Subscriber ID

Displays the identifier by which the subscriber is known.

Line Port

Displays the chassis, slot number, and port number to which the subscriber ID is associated.

CAP ATU-C Port

Displays the chassis, slot number, and port number with which the line port is connected.

Modem Status

Displays whether the modem is trained, training, or not trained.

Pool

Displays the physical or logical pool of which the line port and CAP ATU-C modem port are members.

Actual Up

Displays the actual upstream train rate at which the subscriber is training. This rate can never be higher than the value in the Provisioned Up column.

Actual Down

Displays the actual downstream train rate at which the subscriber is training. This rate can never be higher than the value in the Provisioned Down column.

Rx SNR

Signal-to-noise ratio for ADSL upstream (receive side) data channel.

Provisioned Up

Displays the upstream rate set by the CO, which is the maximum upstream rate at which the subscriber can train.

Provisioned Down

Displays the downstream rate set by the CO, which is the maximum downstream rate at which the subscriber can train.

Provisioned Down Margin

Displays the downstream noise margin that you have provisioned for the subscriber.

Provisioned Up Margin

Displays the upstream noise margin that you have provisioned for the subscriber.

Actual Up Margin

Displays the upstream noise margin that actually occurs within the margin that you have provisioned for the subscriber.

Actual Down Margin

Displays the downstream noise margin that actually occurs within the margin that you have provisioned for the subscriber.

The Active Connections dialog box includes the fields that you have provisioned for upstream and downstream bit rates, actual trained upstream and downstream bit rates, and the received signal-to-noise ratio. In addition, the dialog box includes totals of active connections by pool and the current usage level of each pool.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Feb 16 08:25:37 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.