|
|
This chapter describes the three Cisco 6100 configuration styles and describes step-by-step instructions for provisioning a Digital Off-Hook (DOH) configuration.
Service provisioning is the process for naming subscribers and assigning them to physical and logical pools where they receive ADSL service based on their configuration style. A prerequisite for service provisioning is that a management connection must exist for ViewRunner for HP OpenView to provision the Cisco 6100. A Cisco 6100 must therefore contain at least a Cisco 6100 multiplexer chassis (MC) and a system controller (SC). During the provisioning process, operator-entered information is sent immediately to the Cisco 6100 via SNMP set and get messages. If the management connection is not communicating properly, lost SNMP messages will retry but eventually will be dropped.
The configuration styles for the Cisco 6100 are:
The general steps for provisioning the Cisco 6100 for the DOH configuration style are listed below:
Step 1 Create logical pools.
Step 2 Assign ATU-C and LIM ports to logical pools. (Ports must be locked during assignment.)
Step 3 Associate subscribers to LIM ports.
Step 4 Define CAP RADSL attributes on the Subscriber Properties dialog.
Step 5 Assign subscriber VPI/VCI addresses.
Step 6 Unlock entities.
Step 7 View the Pool Properties dialog to verify the proper configuration.
Each of these steps are covered in detail in the following sections. These steps can be executed only after all components have been successfully auto-discovered.
Service provisioning must adhere to a variety of configuration rules, which prevent errors when establishing ATM connections. ViewRunner for HP OpenView includes service provisioning logic to assure valid combinations of configuration data.
Subtending is a Cisco 6100 feature which reduces the cost per subscriber by amortizing the expense of the network interface (NI) module and the edge switch port connection over a large number of subscribers. Subtending is the service and aggregation of data from one or more "downstream" Cisco 6100s to a "host" Cisco 6100 to further oversubscribe the NI. Subtending enables the service provider to amortize an expensive network component (the broadband interface and terminating ATM edge switch port) over a large number of tariffed subscribers.
The following diagram illustrates the connections of a subtended Cisco 6100 with six subtended Cisco 6100s:
The following figure shows valid address ranges for each Cisco 6100.
While the valid address space shown above indicates that up to 9600 VCCs can be supported, the number is constrained by several factors. First, as the software content increases with each new release, a greater percentage of existing SC and NI RAM is consumed by resident application code.
For Release 2.x of the Cisco 6100, a maximum of 1600 VCCs within the valid address space is recommended. Software limits are not be built in due to the temporary nature of this ceiling.
Subtending in this release requires a node-by-node PVC provisioning. Transit PVCs are used to carry subtended traffic. You bundle multiple PVCs for carriage across the ATM fabric in a subtending Cisco 6100. Up to 32 transit subscribers can be defined per Cisco 6100, however, there must be at least one on each subtend port. Unlike other subscribers, they do not have to be Locked to have PVCs added to or deleted from them. The transit PVCs provide a one-to-one mapping to subscriber PVCs from the subtended Cisco 6100s.
The configuration database can be downloaded from or uploaded to a Cisco 6100. This provides the following benefits.
Wizards lead you through the process of download/upload. See "Configuration Save and Restore" for more information.
A logical pool is a logical grouping of modems and lines. This grouping is used to achieve a particular concentration of subscriber lines to ATU-C modems, for example, 1:1, 2:1, or 6:1. For DOH installations, up to three logical pools can be defined per physical pool.
The MC is divided into two physical pools: A and B. Physical pool A consists of every component in the top half of the chassis and physical pool B is the bottom half. Chassis partitioning into physical pools A and B cannot be changed.
The following figure shows the partitioning of the physical pools in the MC.
Each LCC and POTS splitter chassis (PSC) is also divided into physical pools. Physical pool A is the left half of the chassis and Physical Pool B is the right half. Logical pools are constrained to physical pools; that is, a logical pool may only contain lines and modems from modules plugged into a specific physical pool. For more information on physical and logical pools, see the Cisco 6100 Set Up and Installation Guide.
The following figure shows the physical pools for the LCC.
The following figure shows the physical pools for the POTs splitter chassis (PSC).
To create a logical pool, right click on the MC and select the Pool Properties option, or select the Pool Properties option from the Configuration menu.
The Physical Pool configuration screen appears. This dialog uses two-tiered tabbed property sheets to represent the physical and logical pools. An outer pair of tabs will allow selection of either physical pool A or B.
If no pools have been assigned, the top portion of the Pool Properties window (see Figure 4-7) will be blank.
To create a logical pool, click the Add Pool Now button. The Logical Pool tab appears:
Within a physical pool tab, a second set of tabs displays depicting the logical pools configured for that physical pool. Logical pool tabs start with logical pool 1 up to logical pool 2.
The dialog displays a variety of statistics describing the configuration of the logical and physical pools. Running totals or summaries of pool assignment describe the characteristics of the ports and subscribers assigned to the pools. Over subscription ratio (OSR), a key statistic in DOH configurations, is calculated using three formulas each of which provide a different view of over subscription. These calculations are kept current for each logical pool. The statistics are initially displayed when the logical pool tab is selected. All statistics get recalculated and updated onscreen whenever you assign or deassign an ATU-C or LIM port from the logical pool.
The table below provides field descriptions for this screen:
| Field/Button | Description |
|---|---|
Add Pool Now | Up to three logical pools can be provisioned per physical pool using the Add Pool button. Tabs display in the order in which you create them. Therefore, if logical pools 1, 2, and 3 exist and 2 is deleted, then logical pool 3 becomes logical pool 2. |
Delete Pool Now | Deassigns any ports that are currently assigned to the logical pool and then deletes the logical pool. Note ViewRunner for HP OpenView requires all assigned LIM ports to be Locked prior to pool deletion. The Delete Pool button is dimmed unless this condition is satisfied. |
Over Subscription Ratios - displays the running total of over-subscription within the currently selected logical pool. Three different over subscription formulas are displayed to provide insight into various aspects of the pool characteristics. The ratios that ViewRunner for HP OpenView provides are described below. | |
Assigned Port OSR | Useful when initially configuring logical pools. This ratio is based on locked entities. Assigned Port OSR effectively displays the target oversubscription provisioning ratio for the pool. Assigned Port OSR equals the number of line ports assigned to the logical pool divided by the number of ATU-C ports assigned to the logical pool. |
Provisioned and Unlocked OSR
| Useful to verify that the system is properly configured and administratively unlocked to support the target OSR. This ratio will be equal to the assigned port OSR when all provisioning needed to support service is completed and the entities are unlocked. Locking ATU-C ports increases the OSR (e.g., 3:1 goes to 6:1). Locking LIMs reduces the OSR (e.g., 6:1 goes to 3:1). Provisioned and Unlocked OSR equals the number of unlocked line ports that are: · Assigned to the logical pool · Subordinate to an unlocked module · Associated to an unlocked subscriber This number is then divided by the number of unlocked ATU-C ports assigned to the logical pool that are subordinate to an unlocked module. |
Provisioned and In Service OSR | Displays the active OSR that the system is experiencing, factoring required configurations, administrative permissions, and the Service State of the pooled ports. This ratio includes the Operational State of the system and will vary as alarms set or clear. Provisioned and In Service OSR equals the number of in service line ports assigned to the logical pool that are also associated to an unlocked subscriber. This number is then divided by the number of in service ATU-C ports assigned to the logical pool. |
Real-time Display of DOH Service Statistics | Displays running totals of several counts and calculated values. The following statistics are initially displayed when the logical pool tab is selected: The number of line or ATU-C ports assigned within the currently selected logical pool and number of line or ATU-C ports unassigned to any logical pool. The number of provisioned unlocked ports. This is the number of ports within each list box that have the necessary Administrative State configuration to provide service. A properly configured port must be unlocked and subordinate to an unlocked module. Line ports have the additional requirement of being associated to an unlocked subscriber. The number of Provisioned and In Service ports. The number of ports that have a Service State of In Service and are provisioned properly to provide service. In Service ATU-C ports are implicitly provisioned properly. In Service line ports must also be associated to an unlocked subscriber in order to be provisioned properly to provide service. Running totals are updated whenever a logical pool is deleted, or when a port is assigned or deassigned to or from a logical pool. Providing these statistics in real time is a key value added ViewRunner for HP OpenView feature. These statistics give a summary view of many of the Cisco 6100's critical service parameters and prevents operational mistakes. For large system configurations, most of the list boxes on this dialog will be filled and have scroll bars. These totals provide a convenient summary to replace scrolling the list box and manually tallying DOH service parameters. |
Once you select a logical pool, the dialog displays the current configuration of the logical pool. The following rules apply to logical pools:
In its initial state, auto-discovered resources (LIM and ATU-C ports) are in their respective unassigned windows. Only LIM and ATU-C ports within a physical pool are candidates for assignment into a logical pool belonging to that physical pool.
The list boxes on the bottom third of the screen display unassigned LIM ports and ATU-C modem ports, respectively. The LIM ports are in the left-hand box, the ATU-C modem ports are in the right-hand box.
To assign these ports to a logical pool, simply select the port(s) and click Assign Ports Now or Unassign Ports Now to configure them into the respective list boxes. ViewRunner for HP OpenView supports multiple selection pool assignment. To use this feature, select a sequential range of ports by first left clicking on the beginning port and then pressing the Shift key combined with a left click on the last port in the range. To select non-sequential list box ports press the CTRL key simultaneously with left clicking the individual ports to be selected.
Each list box displays the port's Access Identifier (AID), which includes the chassis type and number, slot number, and port number to uniquely identify its location within the Cisco 6100. Additionally, each port's Administrative State, Service State, and its supporting module's Administrative State are displayed. In the case of LIM ports, the associated subscriber's Administrative State is also displayed. That field is blank if no subscriber is configured for the LIM port.
Each LIM port must have a subscriber ID associated to it. To add, modify, and/or delete a subscriber, you will use the LIM Module Properties dialog. Use the following steps to perform any of these three tasks.
You can add a new subscriber or modify or delete an existing subscriber. If a subscriber is already associated with a port, a Subscriber ID is displayed on both the port and subscriber configuration dialogs.
Step 1 To access the LIM Module Properties dialog, move the cursor down to a LIM module in the Chassis View and right click on the mouse button. The following pop-up menu appears:
Step 2 Highlight the appropriate port properties menu, then select the Configuration option. The LIM Module Properties dialog appears:
The following table provides field descriptions for this screen:
| Field/Button | Description |
|---|---|
Administrative State | Allows the configuration of the Administrative State, either Unlocked or Locked. |
Subscriber ID | Displays the subscriber record identifier, if configured. |
Circuit ID | Displays the identifier assigned to this copper local loop circuit (not supported in this release). |
Physical Pool ID | Displays the physical pool to which this LIM port belongs. |
Logical Pool ID | Displays the physical pool to which this LIM port belongs. |
Edit Pool | Allows you to edit the logical pool that this LIM port is associated with. |
Add Subscriber | Allows you to add a subscriber to this LIM port. Note This button will change to Edit Subscriber if a subscriber is already associated with the LIM port. |
After opening the LIM Module Properties dialog following the instructions above, execute the following procedures to add a subscriber.
Step 1 Make sure that the module is locked on the Module Properties > Configuration dialog.
Step 2 Then, to add a subscriber, click the Edit Subscriber button. The Subscriber Properties dialog appears:
The following table provides field descriptions for this screen:
| Field/Button | Description |
|---|---|
Administrative State | Displays the Administrative State of the subscriber. Can be Locked or Unlocked. Defaults to Locked. |
Subscriber ID | Subscriber ID is a required ViewRunner for HP OpenView field that must contain at least one alphanumeric character, and up to 20 alphanumeric characters. Its uniqueness is not guaranteed by ViewRunner for HP OpenView. ViewRunner for HP OpenView recognizes and displays subscribers created with NULL Subscriber IDs, but does not allow modification of subscriber configuration parameters unless an alphanumeric character has been entered. Note If you input more that 20 characters for the Subscriber ID, the system beeps at you starting with the 21st character, which informs you that you are exceeding the field length.Changing the Subscriber ID is a non-service affecting operation for the Cisco 6100. For information regarding service-affecting vs. non-service affecting, see "Service Affecting Configuration Rules" section of this manual. You can modify the Subscriber ID field when the subscriber is unlocked. |
Service Provisioning | Allows you to actually set up service fora subscriber. Opens the Service Provisioning window. |
| Subscriber Association to Port Group Box | |
Module AID and | Displays the module and slot numbers of the ATU-C. |
Circuit ID | Allows configuration of an identifier assigned to the local loop. For this release, Circuit ID is not supported and cannot be edited. |
| Service Configuration Group Box | |
Max Allowed Downstream/Upstream Rates: | Limits the maximum trained rate of a subscriber's modem. List boxes allow selection of the valid configuration settings using kbps units. See "Understanding ATU-C Train Parameters" section for more information on training. The default on install is 6dB up and 3dB down. |
Margin Configuration (Downstream and Upstream) | Allows the operator to associate an upstream and a downstream margin value with a subscriber. See "Bit Error Rate and Noise Margin" section for more information on setting the margins. Note Because increasing the margins could cause a line not to train, a warning dialog will appear when you try to change the noise margin. |
Allow 136 K Baud | The 136K baud training rates now can be enabled or disabled through a system wide MIB object. If the 136 baud training rates are disabled, then those selections will be grayed out in ViewRunner and thus not selectable by the user. CAP modules support 136 KBaud training rates, which can be allowed or disallowed when the feature is supported by the SC software revision and the subscriber is locked. If the SC supports per-subscriber provisionable 136 KBaud or does not support ATUCPARMS, the "Allow 136 KBaud" toggle on the Cisco 6100 Properties dialog will be disabled. If the SC supports ATUCPARMS but does not support per-subscriber 136 KBaud, then the toggle is enabled. |
CPE Signature | You can configure per-subscriber CPE signature detection for a LIM module through the Subscriber Properties dialog. You can specify the minimum CPE signature within a range of 0-127. The default is 0 which essentially disables CPE signature detection. If the system controller (SC) revision supports per-subscriber provisionable CPE detection, then the performance dialog displays dashes in the "Non-Timer Failed Trains" column and the total for that column is disabled. There is also a column in the subscriber tab of the performance dialog called "CPE Rejects" which totals the number of CPE signatures which were not detected by the design. In addition, the "Allow non-timer CPE trains" toggle on the Cisco 6100 Properties dialog is disabled unless the SC revision supports ATUCPARMS but does not support per-subscriber 136 KBaud, then the toggle is enabled. |
Timers Subgroup Box |
|
Idle Timeout | If you enable the Idle timer, you can specify the number of minutes that a subscriber can be idle before the connection is dropped. The default is |
PVC Idle Mark | If you enable the Idle Timer, you can specify a PVC Idle Threshold so the subscriber will be disconnected if the PVC falls below the specified number of cells per minute. The default value of the PVC threshold is 15 cells per minute. The range for the PVC threshold is 1 to 2147483647 cells per minute. The PVC threshold is used for low tide monitoring. If the PVC traffic is less than the threshold for the duration of the timer, then the PVC is considered idle and the subscriber is disconnected. If the traffic is more than the threshold, the PVC is considered active. A subscriber can have multiple PVCs. If at least one PVC is active, then the subscriber stays connected. |
Session Timeout | If you enable the Session timer, you can specify the number of minutes that a subsriber can remain connected during any one session. The default is |
Lockout Time | The Lockout time can be set in minutes. If the SC does not support timer settings, then all the fields will be disabled. Otherwise, the fields will be enabled or disabled depending on the administrative state of the subscriber (locked or unlocked). The default setting is 5 minutes. The valid range for the session timer is 1 to 60 minutes. |
Step 3 Enter the name of the subscriber in the Subscriber ID field.
Step 4 Select the maximum allowed downstream and upstream rates from the dropdown menu.
Step 5 Configure upstream and downstream margins.
Step 6 Select the timer type and connection time.
Step 7 Click OK or Apply button to save additions.
Step 8 Repeat for every subscriber you want to define.
You can only add subscribers when a subscriber does not exist for the port. This prevents the assignment of more than one subscriber ID per LIM port.
Use the following procedures to modify subscriber data:
Step 1 Navigate to the Subscriber Property dialog using either logical service oriented navigation or from the LIM Port Property dialog select the Edit Subscriber button.
Step 2 Change the Max Allowed Downstream/Upstream Rates field by clicking on the drop down menu.
Step 3 Change the Margin Configuration downstream and upstream fields by clicking on the drop down menu.
Step 4 Allow or disallow 136K Baud training rates.
Step 5 Enable or disable CPE Signature detection.
Step 6 Set the timer type by selecting or deselecting Idle and Session.
Step 7 Enter a value for the Connection Timeout if an Idle or Session timer is enabled.
Step 8 Change the Administrative State to Unlocked.
Step 9 Click OK or Apply for the changes to take affect.
Use the following procedures to delete a subscriber:
Step 1 Navigate to the Subscriber Property dialog using either logical service oriented navigation or from the LIM Port Property dialog select the Edit Subscriber button.
Step 2 Click on the Delete Now button to delete the subscriber.
The Delete button is dimmed unless the subscriber is locked. If the subscriber's Administrative State has been changed to locked since opening the dialog, and that configuration has not yet been applied, then selecting the Delete button pops up the lock confirmation dialog.
The user can configure various subscriber defaults in this release. The user can set the following:
The parameters for setting these are in the vrconstants.conf file. See the ViewRunner for HP OpenView Installation and Administration Guide for more information on configuration files.
Each subscriber may have multiple permanent virtual circuits (PVCs) provisioned. Each PVC contains both a network side and a subscriber side virtual connection that are known as VCCs. Each VCC has both a VPI and VCI. For more information on assigning VPI/VCI addresses, see "Service Provisioning Rules" section
Each subscriber defined must have a VPI/VCI address associated with it before the subscriber can be unlocked.
Use the following procedures to define VPI/VCI addresses:
Step 1 Click on the Service Provisioning button from the Subscriber Properties dialog (see Figure 4-11). The Service Provisioning dialog appears:
You can add or delete a subscriber's PVC in the Service Provisioning dialog only when the subscriber's Administrative State is Locked. Selecting Delete Now pops up a delete confirmation dialog.
The following table provides field descriptions for this screen:
| Field | Description |
|---|---|
Subscriber ID | Displays (read only) the subscriber associated with the PVCs. |
Subscriber PVC list | Displays a list of the current subscriber's VCCs, including the subscriber VPI/VCIs, connected to the Network VPI/VCIs. |
Permanent Virtual Connection Group Box | When the subscriber is locked, you can edit the PVC VPI/VCI values and select the Add Now button to create a new PVC for the subscriber and add it to the PVC connection list, subject to PVC configuration rules. Selecting the Delete Now button deletes the PVC selected in the PVC connection list. The network and subscriber side VPI/VCI list boxes allow selection of valid VPI and VCI combinations, subject to PVC configuration rules. |
Step 2 Enter the VCI/VPI information in their available fields under the Subscriber and
Network group boxes. The subscriber side VPI field defaults to 1 and is not editable.
Step 3 Click on the Add Now button. This takes effect immediately.
Step 4 Repeat for every VCI/VPI address you want to define.
Step 5 Click on the Close button when you are finished.
VCCs may be added or deleted only if the subscriber is locked. Up to four VCCs are supported per subscriber. ViewRunner supports range checking to assure that network side VPI/VCIs are unique.
ViewRunner for HP OpenView provides you information regarding valid and invalid VPI and VCI numbers prior to entering a number. ViewRunner for HP OpenView also displays an error dialog when it detects a network side uniqueness violation.
Use the following procedures to delete subscriber PVCs:
Step 1 At the Service Provisioning dialog, left-click on the subscriber PVC you want to delete.
Step 2 Click on the Delete Now button. This takes effect immediately.
Step 3 Repeat for every PVC you want to delete.
Step 4 Click on the Close button when you are finished.
Once you have entered and verified all logical pool, module, port, subscriber, and VCI/VPI data unlock entities to put them into service. Unlocking simply requires clicking on the Unlocked option in various dialogs and clicking on the Apply button.
Putting a logical pool and provisioned subscriber into service requires unlocking all associated entities:
Step 1 Right click on the ATU-C module and select the Module Properties > Configuration option.
The ATU-C Module Properties screen appears:
Step 2 Click on the Unlocked option. This unlocks the module for service.
Step 3 Click Apply and then OK to return to the Chassis View or to unlock a port, click on the Port tab.
Repeat this same procedure on the LIM modules.
Step 1 Right click on an ATU-C module and select the Port Properties > Configuration option.
The ATU-C Port Properties screen appears:
Step 2 Click on the Unlocked option. This unlocks the port for service.
Step 3 Click Apply and then OK to return to the Chassis View.
Repeat this same procedure on the LIM ports.
Use the following procedures to unlock a subscriber:
Step 1 Position the cursor on the appropriate LIM port.
Step 2 Right click on the Port Properties > Configuration option.
The LIM Port Properties screen appears:
Step 3 Click on the Edit Subscriber... button. The Subscriber Properties screen appears:
Step 4 Click on the Unlocked option.
Step 5 Click Apply and then OK to return to the LIM Module Properties window. The subscriber is now unlocked for service.
If you are subtending Cisco 6100s, you provision the local DOH subscribers and their PVCs just like you do any Cisco 6100 according to the directions above. However, you must also provision transit subscriber and transit PVCs on each of the subtending host Cisco 6100s in the path of each PVC for a subtended Cisco 6100.
Transit subscribers are simply placeholders for bundling transit PVCs. Unlike standard subscribers, they need not be locked to have transit PVCs assigned to or deleted from them. Typically, a single transit subscriber will be assigned to each subtend port, or multiple subscribers could be assigned to aggregate traffic for a specific Cisco 6100 that is subtended from a node. Up to 32 total transit subscribers may be defined per Cisco 6100.
The transit PVCs on the subtend port will have the same VPI/VCI as the subtended PVC did on the network interface side on the subtended Cisco 6100. The VPI/VCI that the transit PVC is cross-connected to on the subtending Cisco 6100's network interface must either be connected to another transit PVC on another Cisco 6100, or to the target VPI/VCI on an ATM edge switch. The following figure illustrates an end-to-end PVC across a subnetwork of subtended Cisco 6100s.
In the figure, Subscriber x on Cisco 6100 no. four has a PVC y that is connected to a LIM or ATU-C port on VPI=vpi1/VCI=vci1. Within Cisco 6100 no. four, this PVC is cross-connected to the NI on VPI=vpi2/VCI=vci2. On Cisco 6100 no. two, a Transit subscriber w is defined to which Transit PVC z will be added. Transit PVC z will have its ingress side connected to the same VPI/VCI as the egress side of the PVC from Cisco 6100 no. four, VPI=vpi2/VCI=vci2. The cross-connection within Cisco 6100 no. two is then to VPI=vpi3/VCI=vci3 on Cisco 6100 no. two's NI. Finally, Cisco 6100 no. one takes in the PVC on Transit subscriber m, Transit PVC n. Transit PVC n connects VPI=vpi3/VCI=vci3 on the subtend port to VPI=vpi4/VCI=vci4 on the network interface and on into the ATM cloud.
To add a transit subscriber, use the following procedures.
Step 1 Go to the 6100 Chassis View of the Cisco 6100 which is to be the host (pass through) for the subscribers on the subtended Cisco 6100(s). Right click on the STM and choose the Port Properties > Configuration option.
Step 2 The STM Port Properties dialog appears. Choose the Add button to add a transit subscriber.
Step 3 A dialog box appears where you specify the subscriber ID for the transit subscriber. Enter the ID and press OK.
Step 4 The new subscriber appears in the list of subscribers. Highlight the new subscriber, and press the Edit button.
Step 5 The Subtend Host Service Provisioning dialog opens for you to provision the transit subscriber according to guidelines found elsewhere in this manual.
You will notice that it is similar to the local service provisioning dialogs, but it labels the subscriber side VPI/VCI connection fields as "Transit Subscriber VPI/VCI".
The following series of steps enable you to determine the presence of a non-interrupted data path between your Cisco 6100 and far-end equipment. More specifically, this test determines whether or not your system has IP connectivity through the ATM network to a far-end server via the Cisco FireRunner.
There is also a preliminary test for the system found in the appendix "Connection Test Procedures for the Cisco 6100 Digital-Off Hook Configuration".
In addition to the cabled up Cisco 6100 chassis to be tested, the following items are necessary.
To set up the Cisco 6100 for testing, follow the steps below:
Step 1 Configure the Cisco 6100 with 1 SC, 1 NI, 1 ATU-C, 1 LC, 1 LIM, and 1 POTS splitter. The LIM and POTS modules need to be inserted into the slot that supports the local loop you want to test. See the Cisco 6100 Set Up and Installation Guide for detailed information on the special subscriber tip/ring mapping to a particular LCC/PSC slot or port number.
Step 2 Using ViewRunner for HP OpenView, configure the module, port, and subscriber to be tested per the provisioning steps detailed in this chapter.
Step 3 At the Main Distribution Frame (MDF), punch down the RJ-11 cable to the subscriber port that is to be tested. Connect the subscriber line to the CPE POTS splitter.
Step 4 Using the other RJ-11 cables, hook the telephone and ADSL line into the CPE POTS splitter as outlined in the CPE documentation.
Use the following procedure to test for connectivity:
Step 1 Power the Cisco 675 LIM ports on. Verify that the associated LIM port detects DOH by lighting the LIM port's LED. Once this has occurred, watch the MC for a blinking ATU-C. Verify that the ATU-C trains up to the 675 by checking the LEDs on the ATU-C and the 675. The ATU-C and 675 (ATU-R) are trained with the ATU-C blinking port LED goes solid and when the 675's WAN link LED goes solid. This verifies subscriber connectivity through the MDF, the PSC and through the LIM and to the ATU-C.
Step 2 Next, verify the telephone receives dialtone and outgoing calls can be established. Verify that incoming calls ring the phone.
Step 3 For IP connectivity, try pinging the server from the laptop once the Cisco 675 has successfully trained. Follow the ping procedure documented in the Cisco 675 Installation and Operation Guide. If the system responds to your ping request with an acknowledgment, end-to-end connectivity has been successfully established between the Cisco 675 and FireRunner. This also validates a current Cisco 6100 configuration and subscriber line connection. This establishes complete connectivity from the MDF to the Cisco 6100 and from the Cisco 6100 to the PSTN.
Posted: Fri Apr 23 14:25:43 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.