cc/td/doc/product/rtrmgmt/cdm/cdm34
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring the System
Setting Date and Time
Setting Trap Recipients
Setting In-band Management Options
Creating Routing Tables
Setting EPD Thresholds
Saving and Restoring System Configuration Data and Downloading System Software
Creating Pooled Configurations

Configuring the System


This chapter describes how to configure and manage the Cisco 6100 Series System with NI-1, including how to set date and time variables, trap recipients, and in-band management options; how to create routing tables; how to download system software for the node; and how to create a line controller chassis and a module for digital off-hook (pooled) chassis configurations.

This chapter includes the following sections:

You can access the windows for most of the procedures in this chapter through the object menu that is shown in Figure 4-1.


Figure 4-1   Object Menu


Setting Date and Time

The hosts for DSLAM configurations are Unix servers and synchronize to a server clock. However, the DSLAM nodes are not synchronized to this clock. The DSLAMS must maintain their own time, which you must set through the management software.

To set or change the date and time for your system, complete the following steps:


Step 1   From the left side of the Map Viewer window, within the C61xxChassisView, right-click C6100v30ManagedElement[DSLAM name] to access the object menu.

Step 2   Choose Open Set Date and Time Dialog from the bottom of the object menu.

The Set date and time dialog window, which is shown in Figure 4-2, opens.


Figure 4-2   Set Date and Time Dialog Window


Step 3   Enter the date using the yyyy month dd format in the Date (yyyy month dd) field; you can use the down arrow to select the month.

Step 4   Enter the time in the Time (hh mm ss) field; you can tab over to each of the hour, minute, and seconds areas.

Step 5   Click Set Date and Time.

Step 6   Click Yes in the Confirmation dialog box.

An Action Report window opens to inform you of success or failure.



Setting Trap Recipients

This section describes how to set alarm traps and includes the following topics:

You can set a managed element to receive alarm notification from its associated server by setting trap recipients. The settings that you choose specify which level of alarms you want the managed element to receive.

Alarm severity levels are as follows:

Trap levels work as follows:

Set Traps Level Receives

Informational

Informational, Minor, Major, and Critical

Minor

Minor, Major, and Critical

Major

Major and Critical

Critical

Critical

NoAlarms

None

To set trap recipients for a managed element, complete these steps:


Step 1   From the left side of the Map Viewer window, right-click over the managed element for which you want to specify trap recipients to access the object menu.

Step 2   Choose Open Create/Delete Trap Recipients Dialog near the bottom of the object menu.



The Add/Delete Trap Recipient window, which is shown in Figure 4-3, opens.


Figure 4-3   Add/Delete Trap Recipient Window


Figure 4-4 shows the fields that display when you scroll to the right side of the Current Trap Recipients Info area.


Figure 4-4   Right Side of Current Trap Recipients Info Area


The Current Trap Recipient Info group box displays the current trap recipient settings as follows:


Note    With this release of CDM, the settings that display in the Current Trap Recipient group box fields are read only. To change the setting for a trap recipient server, you must delete it and then create it with the new setting.

Adding Trap Recipients

You can add up to ten trap recipients. Refer to Figure 4-3. Complete these steps to create a new trap recipient:


Step 1   Enter the following information in the fields on the Create New Trap Recipient group box:

    a. Enter the server IP address in the Trap IP Address field.

    b. Use the down arrow to select severity level in the Trap Rcvr Min Severity field of either Info, Minor, Major, Critical, or No Alarm.

    c. Use the down arrow to select Enabled or Disabled in the Trap Rcvr Std Enable field.

If you select Enabled in this field, the recipient can receive the following SNMP traps:

    d. Use the down arrow to select Enabled or Disabled in the Trap Rcvr Auth Enable field.

This setting is for enabling or disabling the authentication-failure traps. If you select Enabled, it allows the recipient to receive traps when the software tries to access the 6100 MIB using an invalid community string.

Step 2   Click Create New Trap Recipient.

A confirmation dialog box opens asking you to confirm that you want to create this trap recipient.

Step 3   Click Yes to create the new trap recipient.

An Action Report window opens to inform you of success or failure.

Deleting Trap Recipients

Refer to Figure 4-3. Complete these steps to delete a trap recipient:


Step 1   Enter the TrapRcvr Index number of the recipient to be deleted in the Delete Trap Recipient field, then click Delete Trap Recipient. (The index number is listed in the TrapRevrIndex column in the Current Trap Recipients Info group box.)

Step 2   Click Yes to delete the new trap recipient.

An Action Report window opens to inform you of success or failure.



Setting In-band Management Options

You can use in-band management to control and manage the Cisco DSLAM chassis through the ATM channel, rather than through the Ethernet port. The only difference between using the Ether port and the in-band channel is that instead of using conventional Ethernet physical media to communicate to the Cisco DSLAM, CDM uses ATM as the physical layer for communication.

To run IP over ATM, the system uses RFC 1483, Multiprotocol Encapsulation over ATM Adaptation Layer 5 in Logical Link Control (LCC) encapsulation mode. This encapsulation allows data transport through the use of multiple protocols over a single virtual connection.

To set the in-band management channel options, follow these steps:


Step 1   From the left side of the Map Viewer window, right-click to open the managed element object menu.

Step 2   Choose Open Inband Management from the object menu.

The Inband Management window, which is shown in Figure 4-5, opens.


Figure 4-5   Inband Management Window


Step 3   In the Enable/Disable Inband Management group box, verify the following fields:

Step 4   Click Enable to set in-band management, or Disable if you no longer want to use in-band management.


Note    If you enable in-band management, you must set the Inband Management Configuration Admin Status to unlocked on the Inband Mgmt/EPD Thresholds tab of the System/Commission/Decommission/Config sync Dialog window.

Step 5   Click Yes in the confirmation dialog box, or No if you want to cancel out of this process.



To set in-band management configuration options, you must open the System Commission/Decommission/Config sync Dialog window, as follows:


Step 1   From the left side of the Map Viewer window, right-click C6100v30ManagedElement to access the object menu.

Step 2   Choose open System Commission/Decommission/Config sync Dialog window from the object menu.

Step 3   Click the Inband Mgmt/EPD Thresholds tab.

The Inband Mgmt/EPD Thresholds tab is shown in Figure 4-6.


Figure 4-6   Inband Mgmt/EPD Thresholds Tab


The Inband Management Configuration area fields are described in Table 4-1. Tooltips display choices for each field for which you must set a value.

Table 4-1   Inband Management Field Descriptions

Field Description

Admin Status

Choose locked or unlocked.

IP Address

Enter IP address for in-band management.

Mask

Enter subnet mask address.

Network VCI

If VPI is set to 1, VCI should be 0 to 1599. If VPI is set to 0 or 2 to 27, VCI should be 0 to 399.

Network VPI

If VPI is set to 1, VCI should be 0 to 1599. If VPI is set to 0 or 2 to 27, VCI should be 0 to 399.

Step 4   Set these fields as described in Table 4-1.

Step 5   From the System/Commission/Decommission/Config sync Dialog window, Inband Mgmt/EPD Thresholds tab, set the Admin Status field to locked.

Step 6   Click SetData to save your changes.




Note   If you are using in-band management, you must create routing tables, which are described in the "Creating Routing Tables" section on page 4-9.

Creating Routing Tables

This section provides instructions for creating routing tables and includes the following topics:

If you are using Ethernet as the method for managing your Cisco DSLAM chassis system, you do not need to create a routing table. If you are using in-band management, a routing table is required for the system to send outbound packets to the correct interface. Otherwise, the return packets would be unable to reach their destinations.

You set up routing tables in the Routing Table Configuration Dialog window, which is shown in Figure 4-7.


Figure 4-7   Routing Table Configuration Dialog Window


Guidelines for Establishing Routing Tables

Some guidelines to follow when you set up routing tables are as follows:

Steps for Creating or Verifying Routing Tables

Complete the following steps to create new routing table entries for in-band management or to verify existing routing tables:


Step 1   From the left side of the Map Viewer window, right-click to access the object menu.

Step 2   Choose Open Routing Table Configuration Dialog from the menu.

The Routing Table Configuration Dialog window, which is shown in Figure 4-9, opens.


Figure 4-8   Routing Table Configuration Dialog Window


Step 3   Highlight the Routing Table entry in the Routing Table Entries field for any routing table that you want to verify.

Step 4   Enter or verify the entries in the following fields:

Step 5   Add the following new routing entries in the Add Routing Entry group box:

    a. Enter the Destination IP address in this field. This is the address of a network device that is receiving data.

    b. Enter the Gateway IP address in this field. This is the address for the routing device.

    c. Enter the Route Mask IP address in this field. This is the IP address for the routing entry mask, or bit combination.

    d. Enter 2 in the Interface field.

Step 6   Click Create New Route Entry.

Step 7   Click Yes in the configuration dialog box.



Steps for Removing Routing Table Entries

Complete the following steps to remove a routing table entry for in-band management:


Step 1   From the left side of the Map Viewer window, right-click to access the object menu.

Step 2   Choose Open Routing Table Configuration Dialog from the menu.

The Routing Table Configuration Dialog window, which is shown in Figure 4-9, opens.


Figure 4-9   Routing Table Configuration Dialog Window


Step 3   Enter the address of the destination server in the Delete Route area Route Destination field.

Step 4   Click Delete Route.

Step 5   Click Yes in the Confirmation dialog box that displays, "Delete Route with given Destination?"



Setting EPD Thresholds

You can set early packet discard (EPD) threshold values for three priority egress queues per subscriber—Voice, voice signalling, and data. When the number of available or empty ATM cell buffers on the egress queue falls to or below the value that you set as a threshold, the EPD function is activated on that queue.

A value of 0 implies that the EPD function is not to be activated until the queue is 100% full. For example, if you set voice to 4, as soon as available ATM cells equal 4 or less, the EPD function is activated.

Complete the following steps to set these thresholds:


Step 1   From the left side of the Map Viewer window, right-click C6100v30ManagedElement to open the object menu.

Step 2   Choose Open System Commission/Decommission/Config sync Dialog to open the System Commission/Decommission/Config sync Dialog window.

Step 3   Click the Inband Mgmt/EPD Thresholds tab.

The Inband Mgmt/EPD Thresholds tab is shown in Figure 4-10.


Figure 4-10   Inband Mgmt/EPD Thresholds Tab


The EPD Thresholds fields are described in Table 4-2. Tooltips display choices for each field for which you must set a value.

Table 4-2   IEPD Thresholds Tab Field Descriptions

Field Description

Voice

Choose 0 to 5.

Data

Choose 0 to 60.

Voice Signalling

Choose 0 to 10.

Step 4   Enter the appropriate value in each of the fields as described in Table 4-2.

Step 5   Click SetData to save your changes.



Saving and Restoring System Configuration Data and Downloading System Software

This section includes instructions for saving your configuration data, restoring your configuration data, and downloading system software, as follows:

Setting the TFTP Path and Configuring the TFTP IP Address

Before you save or restore configuration data, you need to verify or set the path and IP address for the TFTP server, as follows:


Step 1   From the left side of the Map Viewer window, right-click to access the object menu.

Step 2   Choose Open System/Commission/Decommission/Config sync Dialog window to open the system dialog window.

The System/Commission/Decommission/Config sync Dialog window is shown in Figure 4-11.


Figure 4-11   System/Commission/Decommission/Config sync Dialog Window


Step 3   On the System Configuration tab, verify or set the correct path in the Tftp Path field.


Note    You can leave the TFTP path set to null where the node takes /tftpboot/ in the default download directory.

Step 4   Verify or configure the IP address in the Tftp IP Address field.

Step 5   Click setData to save your changes.



Saving Configuration Data

This procedure is useful for saving your configuration and image data before you upgrade your system by downloading new system software. It is also useful to save your configuration data to port to other systems or to backup your system configuration data.

To save your configuration data and image information to a file, complete the steps that follow.


Note   Before you download the new software, make sure that the state of the managed element is Normal.


Step 1   From the left side of the Map Viewer window, right-click over the managed object whose configuration data you want to save, to access the object menu.

Step 2   Choose Open Save/Restore/SWDownload Dialog from the object menu.

The Software Download Dialog window, which is shown in Figure 4-12, opens. Use the Save Element Manager Data area at the top of the window for this procedure.


Figure 4-12   Software Download Dialog Window


Step 3   In the Save Filename with absolute path field, enter the absolute destination path and filename where you want to save the current element manager data; do not enter the .NSS file extension; CDM enters this extension for you.


Note    Make sure that the save path has the correct access rights for the server rather than for the client.

An absolute path and filename might look like the following path after CDM has added the file extension:

/users/cisco/software/c6100nms.NSS

Note    Remember, you should not enter the .NSS file extension; CDM enters this extension for you.

Step 4   Click Save Element Manager to save this file, and then click Yes to confirm that you want to save it.

The Action Report window opens to inform you that the save is successful. The save process may take a few moments. If the save fails due to a timeout, repeat Step 2 through Step 4.



Restoring Configuration Data

This procedure is useful when you have downloaded new system software, when you are porting configuration and image data to new system configurations, or when a situation occurs for which you need to restore the most current system configuration and image information.

Complete the following steps to restore the configuration data that you saved in the "Saving Configuration Data" section:


Step 1   From the left side of the Map Viewer window, right-click over the managed object whose configuration data you want to restore, to access the object menu.

Step 2   Choose Open Save/Restore/SWDownload Dialog from the object menu.

The Software Download Dialog window, which is shown in Figure 4-12, opens. The area of this window that you use for this procedure is the Restore Element Manager Data area, at the bottom of the window.


Figure 4-13   Software Download Dialog Window


Step 3   In the Software System Download window, select the appropriate choice in the Restore Images field:

    a. Select No in the Restore Images field if you do not want to replace the binary images.

    b. Select Yes in the Restore Images field if you want to restore the previous configuration data and binary images.

Step 4   If you selected Yes in Step 3, enter the correct path name in the Restore Filename with absolute path field.


Tip Use the path with the file extension .NSS from Step 3 in the "Saving Configuration Data" section.

The Action Report window opens to notify you whether your download process was successful. This process may take a few moments.


Note    If the software download fails, decommission and then commission the managed element, and repeat this procedure. See the "Commissioning and Decommissioning a Cisco DSLAM Chassis" section for these instructions.



Downloading the Software

Before you download new system software, you should have completed the steps in the "Setting the TFTP Path and Configuring the TFTP IP Address" section. You should also make sure that you have a local copy of the release definition file (RDF) for downloading. You or your system administrator can get the most recent version of the node software from the Cisco web site, www.cisco.com.

Complete these steps to download the new system software:


Step 1   From the left side of the Map Viewer window, right-click over the managed object for which you want to download new system software, to access the object menu.

Step 2   Choose Open Save/Restore/SWDownload Dialog from the object menu.

The Software Download Dialog window, which is shown in Figure 4-12, opens. The area of this window that you use for this procedure is the Software Image Download area in the middle of the window.


Figure 4-14   Software Download Dialog Window


Step 3   In the RDF Filename with absolute path field, enter the absolute path and the RDF filename from which you want to install the new software.

An absolute path name and filename might look like

/users/c6100/RDF_files/c6100-3.0.rdf

Note    You should verify or set the TFTP path and TFTP IP address before you download the RDF file. (See the "Setting the TFTP Path and Configuring the TFTP IP Address" section.)

Step 4   Click Start Software Download, and then click Yes in the confirmation dialog box to start downloading the software.


Note    Once you click Yes, wait for the Action Report Window to appear and display all messages before proceeding to the next step.

After the software successfully downloads, you need to restore the configuration data from your previous system configuration.

Step 5   Enter the absolute path and name of the file that contains the stored data in the Restore Filename with absolute path field.

Step 6   In the Restore Images field, use the down arrow to select No.

Step 7   Click Restore Data, and then click Yes in the confirmation dialog box to begin restoring your configuration data.

The Action Report window opens to inform you whether the file restores successfully.

Step 8   After you receive notification that the restore process is successful, you must open the System/Commission/Decommission/Config sync Dialog window and click Synchronize.



Creating Pooled Configurations

This section provides an overview and instructions for creating pooled configurations and includes the following topics:

Digital Off-Hook, or pooled, configurations only allow for line interface modules (LIMs) and CAP ATU-C ports within the physical pools. Once you deploy a chassis that is set up for pooled subscribers with a line controller chassis, subrack discovery detects the LIM controller, and then you can set up logical pools and subscribers.

Overview of Physical and Logical Pools

The physical pools are designated as 1 and 2. Physical Pool 1 consists of the components in the top-half of the DSLAM chassis, and Physical Pool 2 consists of the components in the bottom-half of the DSLAM chassis. Once you have partitioned a DSLAM chassis into physical pools 1 and 2, you cannot change it. You can delete the chassis and start over, but you cannot change the configuration once you have created it.

Each physical pool can contain three logical pools, with two exceptions. Together, physical pools A and B can contain up to ten logical pools. This grouping provides for a particular concentration of subscriber lines to CAP ATU-C modules, such as 1:1, 2:1, or 6:1.

After you deploy, commission, and synchronize a pooled configuration, the node recognizes the line controller chassis. To view the line controller chassis, scroll down in the Map Viewer window. The line controller chassis view, which is shown in Figure 4-15, displays in the lower part of the Map Viewer window.


Note   You must unlock the line controller before the line interface modules appear in this view.


Figure 4-15   Line Controller Chassis View


Deploying the LIM Controller

This section includes the following topics about deploying the LIM controller:

The node discovers a LIM controller that is already in place, but if you need to add a LIM controller, you must commission and synchronize a LIM controller on the system. First you must unlock the LIM controller, then deploy it by completing the following procedures.

Unlocking the LIM Controller

Complete these steps to unlock the LIM controller:


Step 1   From the left side of the Map Viewer window, right-click C6100v30LIMController below the line controller chassis view map.

Step 2   Choose Open LIM Controller Status/Config.

The LIM Controller Status/Config window, which is shown in Figure 4-16, opens.


Figure 4-16   LIM Controller Status/Config Window


Step 3   In the Admin Status field, use the down arrow to select unlocked.

Step 4   Click Set Data, and then close this window.

Step 5   Right-click over C6100v30ManagedElement from the left side of the Map Viewer window and choose Open System Commission/Decommission/Config sync Dialog from the object menu to open the System Commission/Decommission/Config sync Dialog window.

Step 6   Click Synchronize in the System Commission/Decommission/Config sync Dialog window to synchronize the node so that it recognizes the LIM controller.

The line interface modules can now be viewed on the line controller chassis view as shown in Figure 4-15.



Steps to Deploy the LIM Controller

Complete these steps to deploy the LIM Controller:


Step 1   From the left side of the Map Viewer window, right-click the C6100v30Managed Element from which you want to deploy a LIM controller.

Step 2   Choose Deployment > Deploy Cisco 6100 ADSL from the object menu.

The Deployment Wizard—Templates window, which is shown in Figure 4-17, opens.


Figure 4-17   Deployment Wizard—Templates Window


Step 3   Choose Deploy LIMController under LC Chassis.

The Deployment Wizard—Object Parameters window, which is shown in Figure 4-18, opens.


Figure 4-18   Deployment Wizard—Object Parameters


Step 4   Click Forward to proceed.

The next Deployment Wizard—Object Parameters window, which is shown in Figure 4-19, opens.


Figure 4-19   Deployment Wizard—Object Parameters Window


Step 5   Enter the IP address of the DSLAM chassis node.

Step 6   Enter the Name of the LIM controller in the C6100v30LIM Controller field.

Step 7   Click Forward to proceed.

Step 8   If the Deployment Wizard—Views window opens, as shown in Figure 4-20, click Select to open the Object Selector window and choose the object manager entity for this module.


Figure 4-20   Deployment Wizard—Views WIndow


When you have completed the steps through the deployment wizard, the Deployment Wizard—Summary window opens, which is shown in Figure 4-21, to inform you that the LIM controller is to be deployed.


Figure 4-21   Deployment Wizard—Summary Window


Step 9   Click Forward to continue and deploy the LIM controller.

When the deployment process is complete, the Deployment Wizard—Results window informs you of the results of the deployment process. On the left side of the Map Viewer window, in the Physical hierarchy view, the LIM Controller hierarchy view displays below the managed element under which you have deployed it.

Step 10   Click Finish to close the Deployment Wizard.



Creating a Line Interface Module on a Line Controller Chassis

If line controller hardware is set up when you deploy, commission, and synchronize your DSLAM chassis, the node discovers this hardware. However, if you need to create a line interface module after you have already deployed a DSLAM chassis, you must do it using the Deployment Wizard.

Complete the following steps to create a line interface module (LIM) on a line controller chassis:


Step 1   From the left side of the Map Viewer window, right-click over the relevant managed object to access the object menu.

Step 2   Choose Open System Commission/Decommission/Config sync Dialog to open the System Commission/Decommission/Config sync Dialog window.

The System Commission/Decommission/Config sync Dialog window is shown in Figure 4-22.


Figure 4-22   System/Commission/Decommission/Config Sync Window


Step 3   In the System Configuration Information area, use the down arrow to choose DOH in the Connect Mode field, and then click setData.

Step 4   From the left side of the Map Viewer window, right-click the line controller chassis to access the object menu, which is shown in Figure 4-23.


Figure 4-23   Line Controller Chassis Object Menu


Step 5   Choose Open Create Module Dialog (on LCChassis) to open the Create Module on LC Chassis Dialog window.

The Create Module on LC Chassis Dialog window is shown in Figure 4-24.


Figure 4-24   Create Module on LC Chassis Dialog Window


Step 6   On the left side of the window, highlight the LC chassis on which you want to create a module.

Step 7   Enter the slot number for the module in the Slot Index field where you want to create a line interface module, then click Create Module.

Step 8   Click Yes in the confirmation dialog box to proceed.



Creating and Setting Up Logical Pools

After your have set up physical pools on the DSLAM chassis, you can create and set up logical pools. Complete these steps to set up a logical pool.


Step 1   From the left side of the Map Viewer window, drill down to C6100v30Mgr > C6100v30ManagedElement[name of DOH chassis] > C6100v30LCChassis >
C6100v30PhysicalPool[A or B].

Step 2   Right-click C6100v30PhysicalPool[A or B] to access the object menu.

Step 3   Choose Open Logical Pool Operations Dialog.

The LPool Create/Delete Info Dialog Window, which is shown in Figure 4-25, opens.


Figure 4-25   LPool Create/Delete Info Dialog Window


Step 4   From the PPool Info/Create LPool tab, click Create New Logical Pool.

An Action Report opens to inform you whether the new logical pool has been created.

Step 5   Repeat Step 4 for as many logical pools that you want to create.



Assigning Logical Pools to Ports

Before you can create and set up subscribers, you must assign each logical pool to a port. Complete these steps:


Step 1   From the left side of the Map Viewer window, drill down to C6100v30Mgr > C6100v30ManagedElement[name of DOH chassis] > C6100v30LCChassis > C6100v30LineInterfaceModule[Chassis Index - Slot Number] > C6100v30LinePort-[Chassis Index - Slot Number - Port Number].

Step 2   Right-click C6100v30LinePort-[Chassis Index - Slot Number - Port Number] to access the object menu.

Step 3   Choose Open Line Port Configuration.

The Line Port Configuration Dialog window, which is shown in Figure 4-26, opens.


Figure 4-26   Line Port Configuration Dialog Window


Step 4   In the LPool ID field, enter the pool ID that you want to assign to this port.

Step 5   Click Set Data.

Step 6   Click Yes in the Confirmation dialog box.

The Action Report window opens to inform you whether you have successfully assigned this port a pool ID.



Setting Up Subscribers in Logical Pools

You use the Subscriber Dialog on Line Port window to enter subscriber values. Instructions for setting these values are given in the "Steps for Setting Up Subscribers in Logical Pools" section. Table 4-3 describes the fields in the Subscriber Dialog on Line Port window.


Note   If you click Enable Tooltip from the Options menu, the tooltip feature guides you as you set subscriber values. When you place your cursor over a field, tooltips display the available values for that field.

Table 4-3   Subscriber Properties Dialog Box Fields

Field Description

Subscriber ID

This field is required and must contain 1 to 20 alphanumeric characters. CDM cannot guarantee the number is unique.

CDM recognizes and displays the subscribers that are created with null subscriber IDs. CDM does not allow modification of subscriber configuration parameters unless you enter an alphanumeric character.

Circuit ID

Allows you to configure an identifier that is assigned to the local loop (the phone line that goes to the CPE1). Setting this field is optional. The Circuit ID depends on whether a port is a competitive local exchange carrier (CLEC) or an independent local exchange carrier (ILEC). Adding a Circuit ID suffix to an existing subscriber ID provides you with more line and location detail for a particular subscriber.

Prov Downstream Rates

Limits the maximum downstream trained rate of a subscriber modem. Valid choices display in tooltip.

Prov Upstream Rates

Limits the maximum upstream trained rate of a subscriber modem. Valid choices display in tooltip.

Prov Downstream Margin

Enter the associate downstream margin value for a subscriber. Valid choices display in tooltip.

Prov Upstream Margin

Enter the associate upstream margin value for a subscriber. Valid choices display in tooltip.

Downstream PSD mask

Enter the PSD value to set downstream transmit power in dBm/Hz per subscriber. Verify that the PSD complies with the service provider standards or as specified on the related service order for the subscriber that you are provisioning.

The following PSD downstream ranges are valid:

  • -34 dBm/Hz
  • -37 dBm/Hz
  • -40 dBm/Hz
  • -43 dBm/Hz
  • -46 dBm/Hz
  • -49 dBm/Hz

This setting is unavailable for quad-port STU-C modules.

Upstream PSD mask

Enter the power spectral density (PSD) value to set upstream transmit power in dBm/Hz per subscriber. Verify that the PSD complies with the service provider standards or as specified on the related service order for the subscriber that you are provisioning.

The following PSD upstream ranges are valid:

  • -38 dBm/Hz
  • -41 dBm/Hz
  • -44 dBm/Hz
  • -47 dBm/Hz
  • -50 dBm/Hz
  • -53 dBm/Hz
CAP Parameters

CAPRSC Config

Choose to set this configuration.

17K Baud Enable

Choose to enable 17 K Baud.

68K Baud Enable

Choose to enable 68 K Baud.

136K Baud Enable

Chose to enable 136 K Baud.

Timer Type

Select one of the following timer settings:

  • None
  • Idle
  • Session
  • Both

Session Timer

If you set Session or Both in the Timer Type field, you must enter the amount of time for a session, 1 to 240 minutes.

Lockout Timer

If you set Session or Both in the Timer Type field, you must enter the amount of time for a subscriber to be locked out of a session, 1 to 60 seconds.

Idle Timer

If you set Idle or Both in the Timer Type field, you must enter the amount of time for the subscriber to be idle, 1 to 60 minutes.

PVC Idle Mark

Enter the Idle Mark for the PVC. Valid values range from 0 to 2147483647 cells per minute.

1CPE = customer premises equipment

Steps for Setting Up Subscribers in Logical Pools

To create and set up subscribers in logical pools, complete the following steps:


Step 1   From the left side of the Map Viewer window, below C6100v30LineInterfaceModule, right-click C6100v30LinePort.

Step 2   From the object menu, choose Open Create Subscriber Dialog on Line Port.

The Create Subscriber Dialog on Line Port window, which is shown in Figure 4-27, opens to the Configuration tab.


Figure 4-27   Create Subscriber Dialog on Line Port Window


Step 3   Enter the value in the Subscriber ID field.

Step 4   Enter the value for the Circuit ID field; this field is optional.


Caution   You must enter a value in every field that follows. For fields with the choice of Disabled or Enabled, you must use the drop-down arrow and select either Disabled or Enabled. If you do not manually choose Disabled or Enabled, the value is read as null.


Note    By holding your cursor over each field, you invoke the tooltips, which display valid choices for each subscriber value.

Step 5   Enter a value in the Prov Downstream Rate field to provision this rate.

Step 6   Enter a value in the Prov Upstream Rate field to provision this rate.

Step 7   Enter a value in the Prov Downstream Margin field to provision this rate.

Step 8   Enter a value in the Prov Upstream Margin field to provision this rate.

Step 9   Enter a value in the Downstream PSD Mask field; be sure to enter the - symbol.

Step 10   Enter a value in the Upstream PSD Mask field; be sure to enter the - symbol.

Step 11   For CAP ATU-C modules, select the appropriate choices in the CAPADSL-specific fields as follows:

    a. Select ShortInterleave or LongInterleave in the CAPRSC Config field.

    b. Select Disabled or Enabled in the 17K Baud Enable field.

    c. Select Enabled or Disabled in the 68K Baud field.

    d. Select Enabled or Disabled in the 136K Baud field.

Step 12   In the Timer Type field, enter one the following timer settings:

    a. If you set Idle or Both in the Timer Type field, you must enter the amount of time for the subscriber to be idle, 1 to 60 minutes.

    b. If you set Session or Both in the Timer Type field, you must enter the amount of time for a subscriber to be locked out of a session, 1 to 60 seconds.

    c. If you set Session or Both in the Timer Type field, you must enter the amount of time for a session, 1 to 240 minutes.

Step 13   Enter the value for the PVC Idle Mark field; valid values are 0 to 2147483647 cells per minute.

Step 14   Click Create Subscriber to create these settings for specific modules or subscribers.

A confirmation dialog box opens.

Step 15   Click Yes in the confirmation dialog box.

The Action Report window opens to inform you whether the process is successful.




hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Jan 8 10:01:08 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.