AnyMedia Access System Operations Software for · PDF fileIssue5 July 2001 1 of 50 LUCENT ... 018, 020, 026, 029, 031, 40), R1.11.0.1- ... • F5 AIS • Dying Gasp event on xDSL link

363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5 July 2001

1 of 50

LUCENT TECHNOLOGIES — PROPRIETARYThis document contains proprietary information and is not

to be disclosed or used except in accordance with applicable agreements.

Contents

1. Overview 2

2. Features 3

3. Operating Issues 11

4. Modem (CPE) Operating Issues 18

5. System Configuration 19

6. Turn-Up Procedures 21

7. Operational and Maintenance Procedures 35

8. Software Upgrade Procedures 41

9. Appendix - ATM xDSL Port Numbering 43

10. Appendix - GSI PPP Activation 45

11. Appendix - QoS/Connection Admission Control 47

AnyMedia® Access SystemOperations Software for Broadband Services (AOS-BB): Software Release DescriptionRelease 1.11.1.2Issue 5

2 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 1. Overview

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

1. Overview

The purpose of this software release description is to provide information about the AnyMediaAccess System Operations Software for Broadband Services (AOS-BB). The CDROM with the AOS-BB software is labeled Release 1.11.1.2. The software version number is identified as R1.11.1.2when retrieved from the system. It is compatible with both the NAR FAST Shelf and the International V5 Shelf and can be used for upgrading from R1.7.3.3-(010, 018, 020, 026, 029, 031, 40), R1.11.0.1-(20, 037) or R1.11.1.1-(024, 024.1). Provisioning databases from these releases and from R1.4.0.2-16, R1.4.0.3-(21,21A) may be restored onto AFMs running R1.11.1.2.

The NAR Shelf is compatible with the AnyMedia Access System Graphical System Interface for Broadband Services (GSI) Release 2.2.1-123. The V5 Shelf is compatible with GSI Version 01.04.18-158. Unlike previous versions of the GSI, there are no confirmation messages when provi-sioning AP’s, ports and cross connects. This was done to speed up the operation of the GSI and to reduce the number of “clicks” needed when provisioning. Error messages are still displayed when provisioning with illegal parameters is attempted.

This document covers operations with the LPA911, or LPA941 (IMA) AFM in the International V5 Shelf, the LPA942 (IMA) AFM in the NAR FAST Shelf and the LPA901or LPA920 in the NAR FASTShelf or the International V5 Shelf. For operations with the BAIU Shelf, refer to applicable documen-tation. The examples and procedures in this document assume support via the GSI, not via the Any-Media Element Manager (AEM). The GSI is designed for turnup and local provisioning of a single AnyMedia shelf. In-service maintenance of AnyMedia systems should be done via the AEM. For detailed information on NAR AEM, refer to LUCENT 363-211-458 Issue 1. For detailed information on International AEM, refer to LUCENT 363-211-465 Issue 1.

This document contains the following parts:

• Features of the AOS-BB Software Release 1.11.1.2.• Operating Issues Resolved— This section lists operating issues resolved in Release 1.11.1.2.• Operating Issues — This section lists exceptions in Release 1.11.1.2 to the operating

procedures that are documented in the customer documentation. • System Configuration — This section identifies the hardware/software versions for Release

1.11.1.2.• Turn-Up Procedures — This section lists the recommended steps to turn-up the AnyMedia

Access System.• Operational and Maintenance Procedures — This section provides procedures that will be useful

during the operation and maintenance of Release 1.11.1.2.• Software Upgrade Procedures - This section provides procedures to upgrade to Release

1.11.1.2.

3 of 50

363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2

2. Features Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

2. Features

The following AOS-BB features are being delivered in Release 1.11.1.2.

2.1. Services

• POTS and ADSL service provided by LPA404 combined POTS and ADSL card (NAR only)• POTS and ADSL service provided by LPA810 combined POTS and ADSL card (NAR only)• ADSL over POTS via LPA 400, 400B, 400C, 408, 416, 419 AP• ADSL over ISDN via LPA414, 417AP• SDSL via LPS716 AP• ADSL modem supporting IP over ATM between modem and AP• ADSL modem supporting PPP for ATM• ADSL modem supporting 10BaseT Ethernet between modem and PC• SDSL modem supporting IP over ATM between modem and SDSL AP• SDSL modem supporting 10BaseT Ethernet between modem and PC• PCI slot resident internal ADSL modem• Internet Access via ADSL or SDSL• Remote LAN Access via ADSL or SDSL• AFM multiplexing of ADSL/SDSL access over DS3/E3/E1/DS1 to ATM network• VoDSL telephony via Jetstream’s CPX-1000 gateway (R2.0)• VoDSL telephony via CopperCom• Four-level QoS for applications using the LPA404, LPA408, LPA414, LPA417, LPA416, LPA419

and LPA810 ADSL APs• Four-level (two simultaneous - CBR with nrtVBR or UBR, rtVBR with nrtVBR or UBR)

QoS for applications using the LPS716 SDSL application pack• 50:1 overbooking• Network Timing Reference to the CPE when using the LPA416• Autosensing• F5 AIS• Dying Gasp event on xDSL link failure (modem dependent)

2.2. Capacity

• Up to 15 ADSL AP packs per FAST or V5 shelf• Up to 15 combined POTS and ADSL AP packs per FAST shelf• Up to 15 SDSL AP packs per FAST or V5 shelf• Up to 16 ports per ADSL AP• Up to 8 combined POTS and ADSL ports per AP• Up to 16 ports per SDSL AP

4 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 2. Features

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

• Up to 7 ONUs per V5 shelf• Up to 240 simultaneous lines per FAST shelf• Up to 912 simultaneous lines per V5 shelf• DS3 capacity of 45 Mbps• E3 capacity of 34 Mbps• E1 IMA capacity of 8 E1 feeders (total 16 Mbps)• DSI IMA capacity of 8 DS1 feeders (total 18 Mbps)• Up to 2000 cross-connects (total of VC + VP-only cross-connects)

2.3. Asymmetric Digital Subscriber Line (ADSL)

• DMT• Rate adaptive and explicit rate ADSL-FULL and ADSL-LITE• Compatible with ANSI T1.413 issue 2, ADSL Metallic Interface• ADSL over ISDN compatible with G.992.1, Annex B• ADSL-LITE compatible with G.992.2 • On board diplexers• 32 Kbps to 13.120 Mbps downstream• 32 Kbps to 1440 Kbps upstream

2.4. Symmetric Digital Subscriber Line (SDSL)

• ATM cell transport over 2B1Q-SDSL baseband coding with direct cell mapping• Explicit Symmetric Upstream/Downstream rates from 144 Kbps to 2.3 Mbps• Tip ring pairs 1-16• Interoperability with Conexant chipset-based modems

2.5. Network Interfaces

• DS3 ATM Data interface via LPA901 AFM• E3 ATM Data interface via LPA911 AFM• 10BaseT interface on AFM for loal management operations• DS1 IMA Data interface via LPA942 AFM• VPI supported for In-Band Management Channel (ATM PVC)• Up to 4 Shelf VPIs supported• E1 IMA Data interface via LPA941 AFM• DS1 IMA Data interface via LPA942 AFM• Optical OC3/STM1 AFM feeder interface• OC3/STM1 ATM Data interface via LPA920 AFM

5 of 50


2. Features Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

2.6. Operations Interfaces

• Graphical Systems Interface (GSI)

— Local operations via 10BaseT interface connection

— Local operations via PPP over Serial Console Port supported with NAR GSI 2.2.1-123

— Connection via PC LAN (requires crossover cable for direct connection). Windows NT and Windows 2000 supported with NAR GSI version 2.2.1 only.

— Remote operation over In-Band Management Channel (ATM PVC)

• LEDs

— CP Fault Faceplate LEDs on AFM and ADSL/SDSL APs

— Summary Alarm LEDs on AFM

— Summary LED on Fuse Control Module (FCM)

— CP Fault & Busy LEDs on combined POTS/ADSL AP (LPA404)

• Inventory and LED test interoperability with Graphical System Interface Software for Narrowband Services (GSI-NB). This includes provisioned and unprovisioned AP packs.

• AnyMedia Element Manager (AEM)

2.7. OAM&P Capabilities

• Alarms

— Available via GSI and AEM

— Summary LEDs on AFM and FCM

— Shelf/slot/port information provided in trap messages

• Configuration Management

— Flexible rate adaptation, choice of min/max. range of ADSL rates

— Explicit rate adaptation, choice of four possible ADSL rates

— Explicit rate adaptation for SDSL, choice of 8 symmetric rates for Upstream/Downstream transmission

— Provisioning database backups and restores via GSI and AEM

— Software download/activation to AFM via GSI and AEM

— Provisioning via GSI and AEM

— Circuit pack inventory for AFM and APs

— Provisionable user password for GSI

• Maintenance

— Boot time self diagnostics for ADSL AP, SDSL AP, and AFM

6 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 2. Features

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— Performance monitoring for Feeders

— Performance monitoring for ADSL and SDSL AP transmission

— LED Test via GSI or at CTU or CIU pack in shelf

— On-demand ADSL or SDSL port test via GSI and AEM

— On-demand Corrupt CRC test via GSI and AEM (ADSL-FULL only)

— ATM Traffic Statistics by connection (max. 128 lines reporting Traffic Data)

— Combined DATA and POTS testing by Metallic Test Pair on Trunk Line Work Station

— Support of in-service software upgrade for future releases

— Support of in-service AFM reboot

— Compatibility with Sunrise xDSL test set

— Compatibility with Broadband Loop Qualification Test Head (Tollgrade)

— GR834 testing - requires CTU and COMDAC with R1.7.2.0 or later

• Provisioning

— ATM Traffic Profiles supporting 4 levels of QoS

— Mismatch of Equipment (MEA) state if equipment doesn’t support requested service

— Connection Admission Control (CAC) verifies system can provide requested service

— User-set field for identifying ADSL/SDSL transmission profiles

— User-set field for cross-connect description

— Up to 4 Shelf VPIs allowed

— AP Port deletion

— Choice of Physical Port Mode (Default) or Logical Port Mode for provisioning and maintenance

— RS-232/PPP Console Port for local operations access (2.2.1 GSI only)

— Provisionable line (loop) timing mode for Feeder

• OAMP Features with GSI not fully supported by 1.9 AEM

— ATM Traffic Statistics by connection (max. 128 lines reporting Traffic Data)

7 of 50


3. Operating Issues Resolved Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

3. Operating Issues Resolved

This section lists information pertaining to recognized operating issues from previous releases that are resolved in Release 1.11.1.2.

1. ISSUE: TURNUP

A. When executing a soft-reset, AFM may FAIL.

Resolved.

B. InBand channel may not work after software upgrade or AFM reboot.

Resolved.

C. Database Backup/Restore validation may fail.

Resolved.

D. AFM may reset while software downloads to APs.

Resolved.

E. InBand channel did not work if Subnet mask set to same as 10BaseT port.

Resolved.

F. AFM will not come up at temperature below 0C degree.

Resolved. New Bootroms available for AFMs.

G. May not be able to provision ATM Traffic profiles.

Resolved.

H. Service in Subshelf may not recover from OCP R&R. Data Status reports Subshelf “Dormant”.

Resolved.

I. Database evolution from previous releases does not work. After AFM software upgrade changes to the provisioning may not be accepted.

Resolved.

J. Database evolution via database restore does not work. After restoral of a database created with a previous software image, changes to the provisioning may not be accepted.

Resolved.

K. Cannot change the xDSL Transmission profile assigned to a port without cross connects.

Resolved.

L. Disconnecting a cross connect or inadvertantly trying to create a second cross connect on a port with duplicate subscriber VP and VCC may cause an extraneous cross connect to be cre-ated. This cross connect cannot be deleted even by deleting the AP or port.

Resolved

8 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 3. Operating Issues Resolved

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

2. ISSUE: GSI

A. InBand Channel VPI may not be displayed at GSI after upgrade from previous releases.

Resolved.

B. No traps (autonomous alarms/events) displayed at GSI (or AEM) after connection via InBand.

Resolved.

C. GSI login may be extremely slow.

Resolved.

D. Cannot edit ATM Traffic Profiles from GSI.

Resolved.

E. ADSL Port attenuation and SNR not displayed correctly at GSI.

Resolved.

F. CDVT units are not displayed properly in ATM Traffic Profiles screen.

Resolved.

G. After connecting to shelf via NAR 2.2.1 GSI, the first Event message may not be reported.

Resolved.

H. Main Shelf Turnup provisioning screens open blank after disconnect then reconnect GSI.

Resolved.

I. When logged into the COMDAC using GSI 2.2.1-052, connection to the AFM is denied. If con-necting to the COMDAC after connecting to the AFM, the AFM connection is dropped.

Resolved.

J. If an ADSL profile with not allowed values is created, the profile creation is denied but a profile with a blank name is created.

Resolved.

K. With GSI connected to both COMDAC and AFM, the Broadband Inventory Data display for packs is incomplete.

Resolved.

L. LED display on AFM pack in GSI Shelf View may be incorrect.

Resolved.

3. ISSUE: Maintenance

A. Downstream (ATU-R) TCA reported if Downstream PM data exceeds Upstream threshold andUpstream (ATU-C) TCA reported if Upstream PM data exceeds Downstream threshold.

Resolved.

9 of 50


3. Operating Issues Resolved Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

B. Default ADSL Performance Monitoring Profiles do not display downstream thresholds.

Resolved.

4. ISSUE: QoS

A. Overbooking value cannot be decreased even if the number of connections would allow it to be lowered.

Resolved.

B. Enabling and Disabling Traffic Statistics on a per pack basis may not enable or disable all of the cross connects on that AP.

Resolved.

C. Changing the overbooking factor for UBR to over 10 causes an error.

Resolved.

D. For VBR.3 connections, all non-conforming cells are tagged (cells exceeding PCR are not dropped).

Resolved.

E. After a software upgrade or a restore of a database generated on a previous software load, the Upstream and Downstream Shelf PCR’s reverts to the default values.

Resolved.

5. ISSUE: IMA

A. IMA alarms are not displayed properly.

Resolved.

B. IMA feeder Service State displayed incorrectly. Cannot set Feeders in-service or OOS.

Resolved.

C. Excessive delay on one IMA link may cause the state of other links in the IMA Group to change to inactive.

Resolved.

D. When the IMA group is inhibited from the GSI, the IMA Group Status is reported as insufficientlinks at the near-end. FE reporting correctly receives the status as blocked.

Resolved.

E. Cannot reset (clear) IMA Performance Monitoring counters.

Resolved.

6. ISSUE: ADSL SERVICE

10 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 3. Operating Issues Resolved

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

A. Poor loop performance near maximum loop reach.

Resolved. Loop performance near max. loop changed to emphasize reach over sustaining afixed SNR. Change due to improvement in Reed/Solomon coding gain by ADSL chip vendors, thus no margin adjustment done at Downstream rate 672K. This provides greater loop reach, though long loops may train up with slightly less SNR margin than specified in ADSL profile.

B. Dying gasp not reported from modem.

Resolved.

7. ISSUE: SDSL

A. Polling alarm occasionally reported on SDSL AP, with loss of data service.

Resolved.

8. ISSUE: Telephony/Broadband Interactions

A. When using an LPA416, static may occur on the POTS line when the corresponding ADSL port is not provisioned.

Resolved.

9. ISSUE: Modem (CPE)

A. ADSL Performance Monitoring reports high Downstream ES at 8 - 9Kft on Xavi ISDN modem.

Resolved.

B. LPA416 does not support non-Globespan chipset lite rate modems.

Resolved. The Aztec 800 and the Comtrend CT-500 can used in Lite mode with the LPA416.

C. Xavi ISDN modem does not work with Default Full Explicit Profile.

Resolved.

11 of 50


4. Operating Issues Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

4. Operating Issues

This section lists information pertaining to recognized operating issues existing in Release 1.11.1.2.A suggested work around is provided when available.

1. ISSUE: TURNUP

A. Software download to an AFM may fail.

Work Around: If software download fails, repeat the software download.

B. If an AP is R&R’d during software download, the AP and ports may not recover until download completed.

Work Around: Do not remove or insert packs during software download. R&R AP to recover.

C. Cannot change the ATM Operations Channel. The new value appears in the Global ATM Paramters screen but does not change in the Data System VP Entry Report.

Work Around: Use the value listed in the Data System VP Entry Report for providing commu-nications through the Inband Channel.

D. After changing Port Numbering Mode, GSI Communications screen (connection to shelf) mayopen before AFM completes reboot. Cannot connect to shelf until AFM completes initializa-tion.

Work Around: Wait 15 minutes, then re-connect.

E. Cannot use new xDSL Transmission profile created in Port Provisioning screen of GSI.

Work Around: Refresh the Port Provisioning window to use new Profile. Profiles should always be created from the Profile Provisioning screen, as detailed in Turnup Section 7.12 of this document.

F. Provisioning of a port or a cross connect via the GSI may fail due to empty fields even if all the fields in the screen have been filled in.

Work Around: Click OK on the message and re-input information.

G. On the xDSL Transmission Profile Screen, the Apply Profile button is always grayed out.

Work Around: To use the profile for a port, refresh the Port provisioning screen and then select the profile from the xDSL Transmission Profile pulldown menu.

H. After reconnecting the fiber between the OAP and the ONU, the subshelf service restored event may not be reported, the subshelf operational state may remain Dormant and Data ser-vice may be erratic.

Work Around: Disconnect and reconnect the fiber again to clear the Dormant status.

I. Slot states for APs in the subshelf may not be reported correctly, especially if the equippage changed while the fiber between the OAP and the ONU was disconnected. The shelf view may also display removed APs and may not display inserted APs.

Work Around: Rely on the Operational state to determine if a provisioned slot is equipped.

12 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 4. Operating Issues

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

J. After reconnecting the fiber between the OAP and the ONU, the AP Operational state may be Out Of Service for all APs even though Data is passing.

Work Around: Use the GSI to reset the subshelf. This resets all of the APs in the subshelf.

K. If an LPA400 or LPA400B is provisioned while it is inserted in a subshelf, the AP may never complete initialization.

Work Around: Always provision the AP slot prior to inserting the AP.

L. When provisioning a cross connect in a subshelf, the GSI may retrieve the pack type informa-tion for the corresponding AP in the main shelf. This may lead the GSI to deny the cross con-nect provisioning.

Work Around: Reselect the subshelf and AP slot and click connect again.

M. The system does not distinguish between profiles of the same type (xDSL, ATM or PM) with the same name. The GSI chooses the first profile with that name when making a connection.

Work Around: Always create profiles with unique names.

N. After creating a new ATM Traffic profile, the profile may not be automatically displayed in the ATM Traffic Profiles screen. The default UBR ATM Traffic Profile is displayed instead.

Work Around: Select the new profile from the pulldown menu to display the parameters of the new profile before applying it to a cross connect.

O. The GSI may list the system VPs twice in the Data VP Entry Report.

Work Around: Ignore the second list of VPs.

P. Changes to the shelf OAMVp made in the Global ATM Parameters screen are not reflected in the View System VP Entry Report screen. However, the system is operating using the new shelf OAMVp.

Work Around: Always use the Global ATM Parameters screen to verify the correct value of the shelf OAMVp.

2. ISSUE: GSI

A. In the inventory screen, the circuit pack type is not correct. A generic circuit pack type of ADSLF+L is reported for ADSL APs and a circuit pack type of SDSL is reported for SDSL APs.

Work Around: Log out of the AFM and log into the Comdac. Retrieve the inventory to obtain the correct circuit pack type.

B. Cannot install 1.4.18 B158 GSI on Windows NT or Windows 2000 machines.

Work Around: Must use Windows 95/98 with this GSI.

C. When a customer adds the 2.2.1 GSI to a computer with the Windows NT or Windows 2000 operating system, the GSI may not install or work properly. Run-time error 713 and/or 429 may be returned from provisioning screens.

13 of 50





1---5----10----15----20----25----30----35----40----45---

Work Around: After installing GSI on NT machine, MUST do both of the following actions:

From the Start menu select Run and type: regsvr32.exe msstdfmt.dll

From the Start menu select Run and type: regsvr32.exe scrrun.dll

D. PC running GSI returns Run-time error ‘91’ message or VBAJET32.dll Error message: “The Jet VBA file (VBAJET.dll for 16-bit versions or VBAJET32.dll for 32-bit versions) cannot be found or registry entry is missing try reinstalling the application that returned the error.”

Work Around: According to Microsoft, the solution is to download and run the following files: dcom95.exe (Distributed Component Object Model for Windows 95)

or dcom98.exe (Distributed Component Object Model for Windows 98)

and

mdac_typ.exe (Microsoft Data Access Components)

Files available at http://www.microsoft.com/data/download.htm

Attention Windows 95 Users: DCOM for Windows 95 must be installed before installing MDAC 2.0x or 2.1x. DCOM for Windows 95 is available for download at

http://www.microsoft.com/com/dcom.asp

After completing the above steps please try to run the GSI again.

E. May not be able to connect to AFM via Console port (NAR only).

Work Around: Check that maximum 15-foot serial cable is connected. If repeated attempts to connect fail, try power cycling the PC used. If still no connection, the AFM should be reset.

F. Rebooting a Windows NT PC while connected to the AFM via PPP may cause the AFM to no longer allow PPP connections. If the AFM is reset, the first PPP session may be allowed but subsequent sessions may be denied.

Work Around: Always disconnect the GSI from the AFM before booting the PC. If it becomes necessary to reboot the PC while the GSI is connected to the AFM, disconnect the cable before rebooting.

G. GSI session may become non-functional after setting IP address in Communications window.

Work Around: Always disconnect GSI session then reconnect after setting IP address.

H. GSI connected via Console port may hang after adding or deleting Shelf VP.

Work Around: If GSI appears to be hung (e.g., CommFailure reported, no response), close GSI then re-open and reconnect. Avoid Shelf VP provisioning via Console port.

I. Disconnection from AFM may cause a Run Time error at the GSI.

Work Around: Click OK to close screen. After GSI closes, it can be re-opened.

14 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

J. After AFM reset, the Connect Screen may appear before the AFM has completed its reset. An error message may appear if the AFM is not ready for connection.

Work Around: Wait until the green Active LED lights on the AFM before reconnecting to the AFM using the GSI.

K. Powering the PC while it is connected to the AFM Console Port may cause the AFM to reset.

Work Around: Disconnect the cable from the AFM prior to booting the PC.

3. ISSUE: ALARMS and CONDITIONS

A. Link Down Event message sent for broken link may report HBER instead of LOS for loops longer than 10 Kft of 26 AWG.

Work Around: Ignore the reason code reported for Link Down.

B. Loss of Frame (LOF) alarm may be reported if Feeder Port 2 (daisy-chain) is enabled with no signal or bad signal received.

Work Around: Assume Loss of Signal (LOS) present and check feeder cable or provisioning downstream.

C. Feeder alarm for LOF may not be reported for DS3/E3 or IMA Feeder after restoring Feeder from LOS condition. Data service will not be supported until the mis-framed feeder is fixed.

Work Around: If data service is not recovered after Feeder LOS alarm clears, check for proper framing using a feeder test set. Correct framing format.

D. Attempting to connect to the AFM while it is rebooting will cause a Runtime Error and the GSI to close.

Work Around: Wait until the AFM has completed rebooting and the green LED is lit before connecting to the AFM via the GSI.

E. Failure/Repair of Feeder 1 may generate a Link Down/Link Up events for Feeder 2.

Work Around: Check alarms to verify if Feeder 2 is faulty.

F. After AFM reset, existing Broadband Network Timing Reference alarms may no longer be reported. However, any new Network Timing Reference alarm is reported.

Work Around: Clear any Broadband Network Timing Reference alarms prior to rebooting the AFM.

4. ISSUE: MAINTENANCE

A. AFM does loopback using F4 loopback cells with a loopback indicator value other than 01 hex. These should be discarded.

Work Around: None.

B. Port Test or Corrupt CRC test from GSI may not run. No response displayed at GSI screen.

Work Around: None. GSI session must be closed (CTRL+ALT+DEL), then GSI started again.

5. ISSUE: QoS

15 of 50





1---5----10----15----20----25----30----35----40----45---

! WARNING:Changes have been made to the Bit Rate to Cell Rate conversion factor. When upgrading from a previous release, ADSL profiles may need to be modified to work with the new inputs to the Connection Admission Control Algorithm

A. Traffic Statistics on a VPC will be incorrect after AFM reset.

Work Around: Disable Traffic Statistics on the VPC then re-enable.

B. Dropped cell counts may not be reported in Traffic Statistics if frame bandwidth is exceeded.

Work Around: None.

C. Cross connects using the default QoS ADSL profiles and the default rt-VBR and nrt-VBR ATM Traffic profiles will be denied.

Work Around: Create new ADSL and ATM traffic profiles with appropriate values and use them to provision rt-VBR and nrt-VBR traffic.

D. On the ATM Traffic PM Screen, the Pack pulldown menu lists the AP’s twice. Using the sec-ond instance of the AP to enable or disable traffic statistics will not work.

Work Around: Always select the first instance of an AP in the pulldown menu when enabling or disabling traffic statistics.

E. For VBR.3, the sum of the CLP0 dropped and tagged cells is shown under the cells tagged column in the ATM Traffic Statistics screen. The cells dropped is always shown as 0. This does not affect the operation of the system. These cells are handled correctly.

6. ISSUE: ADSL SERVICE

A. With ADSL Flexible rate adaptation profile, FAST latency mode is implemented with Interleave Depth set to 1 (no error correction).

Work Around: Must use Explicit profile for full support of Interleave Depth with FAST mode.

7. ISSUE: SDSL

A. LPS716 AP Tip/Ring outputs are UL qualified for intra-building exposure only.

Work Around: If the LPS-716 is to be used with lines that exit the building premises, they must be protected by a Nationally Recognized Testing Laboratory (NRTL) listed telecommuni-cations protection device that provides both primary and secondary protection.

B. Port Test on provisioned LPS716 AP port with no modem will fail with message “Port is busy”.

Work Around: If Port Test is needed, must delete the provisioning for the port (Set port to OOS, click Apply, then click Delete Port in Port Provisioning screen).

C. SDSL PM Threshold Crossing Alert (TCA) is reported with PM data count below threshold value in PM profile assigned to SDSL port.

Work Around: Do not use SDSL PM profile with TCAs enabled.

8. ISSUE: Telephony/Broadband Interactions

16 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

A. ADSL Performance Monitoring reports Errored Seconds and Threshold Crossing Alerts (TCAs) during POTS call processing on LPA404 AP

Work Around: TCAs may be avoided by increasing the PM thresholds in the xDSL PM profile.

9. ISSUE: IMA

NOTE:The current system behavior in IMA mode is as follows:Alarming, IMA/ATM traffic, Performance Management are disabled and the feeder output is benign if the feeder administrative state is set to OOS (Out Of Service) or if the feeder is not assigned to an IMA group. Enabling of the above mentioned items is only possible together with the assignment of a feeder to an IMA group.

NOTE:Release 1.11.1.2 supports IMA CTC (Common Transmit Clock) mode only.

— IMA System

A. Soft Reboot on the LPA941/LPA942 results in a hard reboot and a temporary loss of service.

Work Around: After the completion of the reboot, service is restored automatically.

— IMA Operations

B. A small number ATM cells (< 0.2%) are lost in the upstream direction when links are added to an IMA Group that is running data.

Work Around: None

C. IMA Group Timing mismatch alarm is not alarmed. An event message, “IMA group timing sync” appears instead.

Work Around: Monitor the event screen for IMA Group Timing mismatch events.

D. Issue: Asymmetric Operation of IMA Group is not supported.

Work Around: Use only symmetrical IMA Group operation

— IMA Performance Monitoring

E. IMA PM Threshold Crossing Alerts (TCA) are not reported in the GSI event log and are not flagged in the IMA PM reports.

Work Around: Any occurrence that will increment monitored IMA PM parameters will also generate an event or alarm at the GSI. The IMA PM performance reports can be used in con-junction with these notifications to aid in trouble-shooting.

F. The current and previous 24 hours IMA PM registers are reversed.

Work Around: View the previous 24 hours IMA PM registers to determine the current 24 hours IMA PM values. view the current 24 hours IMA PM registers to determine the previous 24 hours IMA PM values.

17 of 50





1---5----10----15----20----25----30----35----40----45---

G. E1/DS1 Performance Monitoring is not reliable. Failure counters do not stop after error is cleared.

Work Around: None

— E1/DS1 Feeder

H. After system initialization, the Operational Port state of all E1/DS1 feeders is set to IS.

Work Around: After changing the feeder Administrative Port state is changed to IS, the cor-rect Operational Port state will be reflected.

I. When the E1/DS1 cable is diconnected, alarms may not be raised on all of the feeders.

Work Around: When more than one feeder alarm is raised, assume that the E1/DS1 cable is disconnected.

— QoS

J. Shelf PCR accepts values up to 80,000 cps. As a result, CAC may overload feeder capacity.

Work Around: Do not set shelf PCR above feeder capacity (up to 8 possible DS1/E1).

10. ISSUE: OC3/STM-1

A. Alarm Indication times do not fully meet standard requirements.

— Clear Remote Defect Indiction RDI after clearing Loss of Signal LOS is exceeding stan-dard time interval by 30 ms.

— Clearing AIS on port 2 after clearing LOS on port 1 is exceeding standard time interval by 40 ms.

Work Around: No work around needed in current proposed network scenario.

B. Missing alarm report when LPA920 timing is in ‘free run’ mode

Work Around: No work around required. In case of loopback or Line Timing failure, the timing source selector is automatically switching to ‘free run’. Only the status is not shown on the GSI.

C. Wrong Alarm, ‘Trace Identifier Mismatch’, raised when Loss of Pointer LOP defect occurs.

Work Around: Operator can ignore ‘Trace Identifier Mismatch’ alarm together with LOP. Addi-tional alarm is not service affecting.

18 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 5. Modem (CPE) Operating Issues

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

5. Modem (CPE) Operating Issues

This section contains issues with specific modems used for ADSL service with the AnyMedia system:

A. ENI 4060 and 5660 modems may lock up (no data service) if loop changed via loop simulator.

Work Around: Must disconnect/reconnect cable to modem or power-cycle modem to recover.

B. ENI 5621 and 3COM Home Connect modems fail ADSL CRC test in downstream direction.

Work Around: Run Corrupt CRC test for maximum of 5 seconds. External test equipment may be used to test the integrity of the ADSL link in the downstream direction.

C. Low throughput on ENI 5621 with Default Flexible Profile at loops < 10Kft.

Work Around: Create ADSL profile with lower maximum rates for this modem

D. ADSL PM ES hits reported from 5621, 5660, 3COM 918 modems with Default Explicit profile

Work Around: Use Explicit profile with lower maximum rates

E. Downstream SNR and Attenuation = 0 with Default Explicit profile on Alcatel-based modem.

Work Around: Use Explicit profile with maximum downstream rate 7424 Kbps.

F. ADSL Performance Monitoring reports high Upstream Errored Seconds (ES) with ADSL-LITE profiles on ENI 5621or 3COM HomeConnect modem.

Work Around: Use Aztech 800 or COMTREND CT-500 modem for ADSL-LITE.

G. ADSL Performance Monitoring reports high Upstream ES at 4Kft 26 AWG on Alcatel Speed-Touch modem with LPA404B AP (NAR).

Work Around: None.

H. Downstream Attenuation reported from Xavi ISDN modem is incorrect.

Work Around: To get correct Attenuation, divide the reported value by 2.

I. ADSL PM reports high Errored Seconds on Xavi ISDN modem with short loops (< 500 feet).

Work Around: For short loops, use ADSL transmission profile with 48 in PSDM field.

J. SDSL data may not recover from short (<2 seconds) cable glitch with CellPipe 50S modem.

Work Around: Data recovered by toggling port OOS/in-service, or turning modem on/off.

K. LPA416 link stability (i.e. error performance) may not be optimized with data profile interleave depth set to “1” when using non-Globespan chipset ADSL modems.

Work Around: Increase data profile interleave depth up to a maximum of 64 for non-Globe-span chipset ADSL modems to improve error performance, thereby, reducing probability of link retrain.

L. When retrieving data status for ADSL modems with ADI-918 chipsets connected to a LPA416, the downstream attenuation value will be incorrectly displayed as “0”.

Work Around: None.

19 of 50


6. System Configuration Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

6. System Configuration

6.1. Equipment Compatibility

The following table lists the version of AnyMedia equipment that is compatible with Release 1.11.1.2.

** LPA400 not support Alcatel inter-operability and ADSL-LITE compatibility with G.992.2

*** POTS/ADSL service requires COMDAC software R1.2.2.5 or R1.7.1 or greater.

Type Model Series/Version Description

OC3/STM1 AFM LPA920 S1:2 Asynchronous Transfer Mode Feeder Multiplexer

DS3 AFM LPA901 S1:3 Asynchronous Transfer Mode Feeder Multiplexer

E3 AFM LPA911 S1:3 Asynchronous Transfer Mode Feeder Multiplexer

E1 IMA AFM LPA941 S1:3 E1 Inverse Multiplexing over ATM AFM

DS1 IMA AFM LPA942 S1:2 DS1 Inverse Multiplexing over ATM AFM

ADSL AP LPA400 S2:2, S2:3,S2:4**

Asymmetric Digital Subscriber Line Application Pack

ADSL AP LPA400B S1:1 Asymmetric Digital Subscriber Line Application Pack

ADSL AP LPA400C S1:1-1:3 Asymmetric Digital Subscriber Line Application Pack

POTS/ADSL AP LPA404B S1:1*** Asymmetric Digital Subscriber Line/ POTS Application Pack (4-line)

ADSL AP LPA408 S2:2-2:6 Asymmetric Digital Subscriber Line Application Pack (8-line)

ADSL/ISDN AP LPA414 S3:3-3:4 Asymmetric Digital Subscriber Line over ISDN Application Pack (4-line)

ADSL AP LPA416 S4:4 Asymmetric Digital Subscriber Line Application Pack (16-line)

ADSL/ISDN AP LPA417 S1:1 Asymmetric Digital Subscriber Line over ISDN Application Pack (16 -line)

ADSL AP LPA419 S1:1 Asymmetric Digital Subscriber Line Application Pack (16-line)

POTS/ADSL AP LPA810 S1:1 Asymmetric Digital Subscriber Line/POTS Application Pack (8-lineADSL/32-line POTS)

SDSL AP LPS716 S1:1 Symmetric Digital Subscriber Line Application Pack (16-line)

20 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 6. System Configuration

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

6.2. Software Compatibility

The following table lists the versions of COMDAC, GSI, and AEM compatible with AnyMediaR1.11.1.2.

6.3. Customer Premise Equipment Compatibility

Refer to Customer Technical Support for the latest information on ATM xDSL CPE modems that are currently supported.

AnyMedia Shelf COMDAC SW GSI AEM

FAST (NAR) 1.2.2.5, 1.7.1, 1.7.2 R2.2.1-B123 R1.9 load 69.2.4

V5 (International) 1.4, 1.6 R1.4.18-B158 R1.9 load 59.2.4

21 of 50


7. Turn-Up Procedures Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

7. Turn-Up Procedures

This section describes the recommended steps to turn-up a new DS3 or E3 system. For the “official” procedure, refer to the Command and Procedures manual (363-211-103). For procedures to turn-upOC3/STM1 system, E1 IMA system, DS1 IMA system, ONUs, Daisy-chained system or for detailed information on QoS provisioning, refer to the Command and Procedures manual.

! WARNING:When removing or inserting a pack always wait 15 seconds before removing or inserting the same or another pack.

NOTE:This procedure assumes that initially, no packs have been inserted into the shelf, no cables have been attached to the packs and that the AFM contains software load 1.11.1.2. If existing AFM (R1.7.3.3) is being upgraded to R1.11.1.2, refer to procedures in Section 9 on page 41.

NOTE:The IP address used in this section is assumed to be the LAN (10BaseT) address. For set up of the In-Band Management Channel, refer to Section 8 - Item 8 Setting up an In-Band Man-agement Channel.

NOTE:The pull-down menu sequence Provisioning ==> System Turnup ==> Data ==> Main Shelfassumes the 2.2.1 GSI. With the 1.4.18 GSI, sequence is Provisioning ==> System Turnup ==> Main Shelf ==> Data

1. Installation of AFM

A. Obtain the default IP address from the AFM. If the IP address is already available, skip to Step B

B. Open a HyperTerminal window on your PC. Under the File-->Properties menu, configure the settings. Set the baudrate of the terminal for 57,600 Bps, Stop Bit to 1, Data to 8 bits, Parity to None, and the Flow Control to none.

— Prior to inserting the AFM into the system, connect the PC running Hyper Terminal (or a dumb terminal) to the console port on the AFM. This requires a straight-through DB9 cable from the COM1 port on the PC to the AFM. While the AFM is initializing, the IP address will appear in the Hyper Terminal window.

— Remove the cable between the AFM and Hyper Terminal.

C. Plug-in AFM pack into slot marked AP-16/AFM.

22 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 7. Turn-Up Procedures

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— Wait at least 15 minutes for the AFM to complete it initialization. During this time:

— If a PC is connected to the console port, the current IP address (e.g., 192.168.160.160)will appear on the terminal connected to the console port in approximately 5 minutes. Once the IP address has been obtained, the connection to the console port may be bro-ken.

— All lights initially are lit on the AFM, then FAULT LED blinks at a 1 per second rate dur-ing initialization. This flashing will last about 10 minutes. FAULT LED may remain on or off for a few minutes during the initialization.

— When initialization has completed the ACTIVE, CR-MJ, and CLF1 LEDs will remain on. It may take up to 15 minutes for these LEDs to appear on the AFM.

D. Connect the feeder TX output from the Broadband Network (e.g., switch or router) to the RX-1 jack on the AFM pack.

E. Connect the feeder RX output from the Broadband Network (e.g., switch or router) to the TX-1 jack on the AFM pack.

— If the Broadband Network (e.g., switch or router) has been configured correctly, the CR-MJ and CLF-1 LEDs will turn off indicating an active connection to the switch. This may take up to 3 minutes. If the LEDs do not clear, check the Broadband Network feeder configuration.

F. To test the connection to the ATM network (optional):

— Remove RX-1 connection: CLF-1 turns on indicating received loss of signal. After about 10 seconds, CR-MJ LED is lit. Restore RX-1 connection. Observe CR-MJ and CLF-1 LEDs turn off

2. Connecting GSI to System

(assuming latest GSI software is already loaded onto PC - see procedure in Section 9 on page 41)

If Connecting to 10BaseT:

A. Turn on PC.

B. Connect an Ethernet crossover cable with a module RJ45 cable between the GSI PC Ethernet output port to the AFM 10BaseT port. This connection can also be made through a hub. In this case, your PC must be configured with the proper IP address (e.g., If the system IP=192.168.160.160, set the PC IP=192.168.160.X where X is not 160) and subnet mask (e.g., Subnet mask=255.255.255.0).

C. Start-up GSI software by clicking on the GSI Icon.

D. In the Menu bar, click the Connect icon at left. The Connect to Shelf window opens. Select AFM.

— In the Select Link window, select the LAN specified in the Work Order.

23 of 50





1---5----10----15----20----25----30----35----40----45---

— In the Host Address entity enter the default current IP address (obtained in Step 1a, e.g. 192.168.160.160, or as provisioned)

— In the SECURITY ID window enter the security ID: public (or as provisioned)

— Click Connect.

— The AnyMedia AFM ADSL: Graphical System Interface Version 2.2.1 or 1.4.18 (Shelf View) comes up. Note, the bottom of the GSI states that you are connected to the IP Address of the AFM plug-in. The GSI/AFM are ready for command inputs.

If Connecting to Console: See Appendix - GSI PPP Activation on page 45

A. Turn on PC.

B. Connect an RS-232 cable (maximum length 15-feet) between the GSI PC serial port to the AFM Con-sole port.

C. Start-up GSI software by clicking on the GSI Icon.

D. In the Menu bar, click the Connect icon at left. The Connect to Shelf window opens. Select AFM.

— In the Select Link window, select the COMx specified in the Work Order.

— In the SECURITY ID window enter the security ID: public (or as provisioned)

— Click Connect.

— The AnyMedia AFM ADSL: Graphical System Interface Version 2.2.1 or 1.4.18 (Shelf View) comes up. The GSI/AFM are ready for command inputs.

NOTE:In most GSI screens, there are 3 buttons at bottom. The Apply button sets the provisioning data on the screen, and returns to same screen. The OK button also sets the provisioning data on the screen, but then exits the window. The CANCEL button exits the window. In some screens a CLOSE button appears. This CLOSE button is the same as the CANCEL button.

3. Initializing System to Default State (Clearing data memory)

! WARNING:After INIT-SYS, the Default Router will be set to 0.0.0.0. If Default Router is needed for remote access, connect GSI via cross-over cable or via console port to AFM and re-provision Default Router.

A. Execute INITIALIZE SYSTEM DATABASE command:

— From menu bar select NE Operations ==> Initialize System

— In the Initialize System window, check the warning box and hit OK.

— Series of confirmation windows open. Click Yes or OK to confirm command. An hourglass will appear indicating the system is busy. This hourglass will remain until the system initialization is complete. The entire process may take up to 20 minutes.

24 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— In about 3 minutes after start of the initialization, all the AFM LEDs come on for about 20 seconds.

— During the next 10 minutes of initialization, the AFM Fault LED will blink at a 1 per sec-ond rate.

— The AFM ACTV light comes up in about 10 minutes. If the ACTV LED is not lit after 20 minutes, remove the AFM and re-insert, then wait another 15 minutes for the ACTV LED to come up.

— Approximately 2 minutes after the AFM ACTV light comes up, the hourglass disappears and the Connect to Shelf window appears at the GSI. When the login is complete, the GSI will show the AFM pack in slot 16.

NOTE:If you cannot connect to the shelf, and the connect command times out, restart the GSI by completing Steps 2c and 2d above after closing the GSI window. Return here after you have logged into the system.

4. Verifying Active Software

A. Verify that the current Active Software is R1.11.1.2

— From the menu bar select NE Operations ==> Software (or SW Download) ==> Activate

— Verify that the Version Now Running is R1.11.1.2 and that the Version Active After Next Reboot is also R1.11.1.2. If the versions are correct, hit CLOSE.

— If the Version Now Running and the Version Active After Next Reboot is not R1.11.1.2, check the Version available for Activation.

— If the Version available for Activation is R1.11.1.2, follow the procedures for Activating Soft-ware and Rebooting AFM in Section 8.6 and 8.7. Reconnect via the GSI.

— If the Version available for Activation is not R1.11.1.2, follow the procedures in Section 8 to Download the correct software version, Activate, then Reboot the AFM. Recon-nect via the GSI.

5. Setting System Information: Site ID (SID), Contact, and Location

NOTE: the SID, Contact and Location are optional.

To set the System Information:

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==>(tab)Main Shelf

— In the Site ID box enter the site id specified in the Work Order. (e.g. AnyMedia AFMADSL)

— Leave Contact box blank unless otherwise specified

— In the Location box enter the location specified in the Work Order. (e.g. LUCENT Technolo-gies)

— Click Apply.

25 of 50





1---5----10----15----20----25----30----35----40----45---

6. Setting Port Numbering Mode

— Enter the Port Numbering Mode as specified in the Work Order. (see Appendix - Section 10 on page 43). Note that the AFM will reboot (GSI must be re-connected) if the Port Numbering Mode is changed.

7. Setting Shelf VPIs and Global ATM parameters

NOTE:If 4th Shelf VPI is added, the AFM MUST be hard-reset (via GSI or R&R) if the shelf has been upgraded from any release before R1.7.3.1-B021.

To set Shelf VPIs (maximum of 4 supported):

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab)Main Shelf

— In the Shelf VP box, click on the default VPI (255). If the Work Order specifies different Shelf VPI(s), enter the VPI specified (e.g., VPI:5). NOTE: this has to match the ATM switch VPI for the feeder. Select the Service Category (use “UBR” unless specified otherwise).

— Click Add. Wait 10-20 seconds for the hourglass to clear.

— If the default VPI 255 is not specified in the Work Order, it should be deleted.

— Select 255 in the Shelf VP box.

— Click Delete. Enter yes to deletion confirmation message.

— Repeat Add procedure for all additional Shelf VPIs specified (maximum of 4 supported)

— If In-Band Management Channel is to be used, refer to procedure in Section 8 - Item 8 to set the ATM Operations Channel VPI

— List of Shelf VPIs can be retrieved from menu bar View ==> Data VP Entry Report

To set Global ATM parameters (for details on these parameters, refer to Customer Documentation):

— From menu bar select Provisioning ==> System Turnup ==> Data ==> (tab)Main Shelf

— Click Global ATM Parameters

— Review parameters displayed. If service order specifies different parameters for Shelf PCR (Upstream/Downstream) enter those parameters. If service order specifies different parame-ters for Shelf Overbooking Factor/Cell Transfer Delay/Cell Delay Variation/Cell Loss Ratio by Service Category, enter those values.

— Click Apply.

8. Setting System Security ID (Optional)

! WARNING:AFM must be reset if Security ID is changed.

To set the Security ID:

26 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab)Communications

— In the Security ID box, enter the Security ID specified in the Work Order.

— Click Apply.

— The new Security ID will not take effect until AFM is reset. See Reboot procedure in Section 8.

9. Setting Autonomous Message Destination

(Optional, Used with Element Manager, etc.)

To set the Autonomous Message Destination:

— From the menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab)Communications

— In the Autonomous Message Destination Text box, type the IP address of the Autonomous Message Destination in the Selected Address box

— Click on Add to add the IP address

— Click on Apply at the bottom to apply changes

10. Setting IP Configuration

(optional operation on new AFM pack - the IP could be the same as the one used to login to the sys-tem). If In-Band Management Channel is to be used, refer to procedure in Section 8 - Item 8.

To set the IP configuration for the LAN:

— From the menu bar select Provisioning ==>System Turnup ==> Data ==> Main Shelf ==> (Tab) Communications

— In the IP configuration text box enter the 10base-T IP address specified in the Work Order(e.g., 135.17.78.37) and note it for reference.

— In the DEFAULT ROUTER text box enter the LAN (10base-T) router address specified in the Work Order.

— In the SUBNET MASK text box enter the LAN subnet mask address specified in the WorkOrder

— Click Apply at bottom to apply changes

To set the IP configuration for the Console Port:

— From the menu bar select Provisioning ==>System Turnup ==> Data ==> Main Shelf ==> (Tab) Communications

— In the IP configuration text box enter the Console Port IP address if specified in the WorkOrder (e.g., 135.17.78.37) and note it for reference.

— In the SUBNET MASK text box enter the subnet mask address specified in the Work Order

— Click Update Mask to apply changes to Subnet Mask, then click Apply at bottom to apply IP changes

27 of 50





1---5----10----15----20----25----30----35----40----45---

11. Setting system date and time

NOTE:After any AFM reboot or shelf power-up, the system date is set back to default of 01/01/70

To set the system date and time:

— 2.2.1 GSI: From menu bar select Provisioning ==> Equipment ==> Data ==> Date/Time

— 1.4.18 GSI: From menu bar select Provisioning ==> Equipment ==> Date/Time

— The Get Current box shows current AFM date/time. Hit Cancel if date/time not to be changed

— In the Set New box, select Set to PC Date and Time to use date/time from PC, or de-select Set to PC Date and Time and enter date/time you want. Click OK to set date/time and close window

12. Provisioning the system for service (method defined in the Work Order)

A. Growth of AP Packs: If the Work Order specifies growth of ADSL or SDSL AP packs, perform the following steps:

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab) Pack

— In the Pack window select the parameters specified in the Work Order

— For Pack parameters are:

- Slot Number: AP1 - AP15 (e.g., AP1)

- Pack Type: ADSL or SDSL

- Configured State: In-Service

— Click Add

— After about 40 seconds, the Apply button grays out.

— Repeat steps for each AP to be grown in

— Close the provisioning window

B. Creation of ADSL and SDSL Transmission Profiles

— From menu bar select Provisioning ==> Profiles ==> xDSL Transmission

— There are 8 default ADSL Transmission Profiles. The first 4 Default profiles may be used for non-QoS lines. The other 4 Default profiles in the list are for use with QoS.

— There is also 1 default SDSL Transmission Profile

— View the parameters for each of the default transmission profiles by selecting in the Profile box. If one of the default profiles is specified in the Work Order or if one of them contains the values listed in the Work Order, select the CANCEL button at the bottom of the screen to exit this window. If none of the default profiles will meet the parameters listed in the Work Order, a new profile must be created. To create a new profile, use the following procedure:

28 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— Select the Default profile with Rate Adaptation matching the Work Order.For example, if ADSL profile with Explicit Rate Adaptation is needed, select Default 4. Click New at the bottom of the window. New ADSL Transmission Profile screen is displayed.

— Fill in the windows according to your Work Order

— Click the Create Profile button

— After 1 - 2 minutes, the new profile will be displayed in the Transmission Profiles screen

— Note the number (and name/label if entered) of new ADSL Transmission profile (e.g., 5)

— If any other profiles are needed, repeat last 5 steps. If no new profiles are needed, hit Cancel to close the window.

C. Performance Monitoring (PM) Profile: There are 4 default profiles, labeled “1-Default 1: All TCAs Disabled”, “2-Default 2: TCAs Enabled”, 127-Default 2: SDSL TCAs Enabled, and 128-Default 1:All SDSL TCAs Disabled. The profiles “Default 1” collects PM data, but will not send Threshold Crossing Alerts (TCAs). If the Work Order specifies setting PM parameters, perform the following steps:

— From menu bar select Provisioning ==> Profiles ==> xDSL Performance Monitoring

— In the “PM Profile” box select “2-Default2” for ADSL or “127-Default2” for SDSL

— Compare the values displayed with the Work Order. If the values listed match those dis-played with the Work Order, close this window. If any values need to be changed, use the following procedure to create a new PM profile.

— Click New at the bottom of the window. New PM Profile screen opens

— Enter new upstream/downstream values from the Work Order

— Click Create Profile

— After about 20 seconds, the new profile will be displayed

— Note number of new PM profile (e.g., 3)

— Click Cancel to close window (or repeat steps if more PM profiles needed)

D. Creation of ATM Traffic Profiles (for Cross-Connect Provisioning)

— From menu bar select Provisioning ==> Profiles ==> ATM Traffic

— There are 8 default ATM Traffic profiles. The first 4 Default profiles are to be used for each of the 4 classes of service on ADSL lines. The other 4 Default profiles in list are for SDSL lines.

— View the parameters for each of the default transmission profiles by selecting in the Profile Name box. If one of the default profiles is specified in the Work Order or if one of them contains the values listed in the Work Order, select the CANCEL button at the bottom of the screen to exit this window. If none of the default profiles will meet the parameters listed in the Work Order, a new profile must be created. To create a new profile, use the following procedure:

29 of 50





1---5----10----15----20----25----30----35----40----45---

— Select the Default profile with Service Category matching the Work Order. For example, if ATM Traffic profile for ADSL with CBR is needed, select Default 2. Click New at the bottom of the window. New ATM Traffic Profile screen is dis-played

— Fill in the windows according to your Work Order. Include a Profile Name

— Click the Create Profile button

— After 1 minute, the hourglass clears.

— If any other profiles are needed, repeat last 4 steps. If no new profiles are needed, hit Cancel to close the window.

E. Feeder Provisioning (DS3/E3): If the Work Order specifies to set feeder port, and feeder port parameters, perform the following steps:

— From menu bar select Provisioning ==>System Turnup ==> Data ==> Main Shelf ==> (Tab) Feeder

— In the Feeder Port box, select Port 1 and verify the parameters displayed. If only one Feeder Port is to be used, it should be Feeder Port 1. Feeder Port 2 is configured in Daisy Chain applications.

— In the Feeder Port Parameters list boxes, start with the default parameters provided and change only those parameters specified in the Work Order

! WARNING:Parameters MUST match router or switch configuration! In particular, verify cell scrambling setting in DS3 or E3, and Frame Format in DS3.

• Set Feeder Port Parameters: DS3 version

— Configuration Status: In-Service (provisionable only for Port 2)

— Cell Scrambling: Enabled or Disabled

— Line Type: C Bit Parity

— Single Bit Error Correction: Enabled or Disabled

— Frame Format: PLCP or HEC

— Line Length: 0-224 or 225-450

— Provision Timing Source: Free Running or Line Time (901 AFM only)

— Performance Monitor Threshold - If Feeder PM is desired, click PM Enable box then select Performance Monitoring Thresholds box and fill in the parameters according to the Work Order. Otherwise, leave blank.

— If changes made, click Apply

— Repeat for Port 2 (Daisy Chain configuration) if specified in the Work Order.

NOTE:Cannot set Timing Source for Port 2

30 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— If Feeder Port 2 is enabled, connect feeder cables from RX-2/TX-2 jacks on the AFM to corresponding TX-1/RX-1 jacks on the downstream (daisy-chained) AnyMedia AFM

• Set Feeder Port Parameters: E3 version

— Configuration Status: Enabled (provisionable only for Port 2

— Timing Source: Free Running or Line Timed (only Free Running if 910 AFM)

— Cell Scrambling: Enabled or Disabled

— Single Bit Error Correction: Enabled or Disabled

— Frame Format: HEC (not provisionable)

— Trailtrace Alarm Enable: true or false

— Provision Timing Source: Free Running or Line Time (911 AFM only)

— Performance Monitor Threshold - If Feeder PM is desired, click PM Enable box then select Performance Monitoring Thresholds box and fill in the parameters according to the Work Order. Otherwise, leave blank.

— If changes made, click Apply

— Repeat for Port 2 (Daisy Chain configuration) if specified in the Work Order.

NOTE:Cannot set Timing Source for Port 2

— If Feeder Port 2 is enabled, connect feeder cables from RX-2/TX-2 jacks on the AFM to corresponding TX-1/RX-1 jacks on the downstream (daisy-chained) AnyMedia AFM

F. Provision IMA Services (LPA941 or LPA942 AFM)

• Set IMA Timing Source:

— Select the Provision->Equipment->Feeder Menu from the GSI toolbar

— Click on the Timing Source sub-tab

— Select the E1/DS1 feeders for Primary and Secondary timing source if values other than the defaults are desired (Primary = E1/DS1 Feeder 1, Secondary = E1/DS1 Feeder 2)

— Click on the Apply button. Wait for the process to complete

• Set E1/DS1 Feeders to In-Service:

— Select the Main Shelf Turnup – System provisioning screen

— Click on the Feeder Port sub-tab

— For each feeder port to be provisioned, select the port number and change the Administrative Port State to IS

— Click on the Apply button and wait for the process to complete. Do not check the PM Enable box during this step. PM should not be enabled until all IMA provi-sioning is completed

31 of 50





1---5----10----15----20----25----30----35----40----45---

— Note - a feeder port must be provisioned to IS before it can be added to the IMA Group

• Provision IMA Group:

— Select the main IMA tab, then select the IMA Group sub-tab

— Select the desired values for the IMA Group Configuration values. Note - Timingmode must be set to CTC

— Click on the Create Group button. Wait for the process to complete

• Add IMA links:

— Select the IMA Link sub-tab from the same screen

— For each IMA link to be added to the IMA Group, select the link number and click on the Add Link button. Wait for the process to complete before adding the next link

NOTE:If an error message is received indicating that there was an error adding the link, refresh the view by selecting the link number again, and verify that the link was not added. If it does not show as part of the group, click on the Add Link button again.

G. Growth of ADSL/SDSL PORTs: If the Work Order specifies growth of Ports, perform the fol-lowing steps:

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab) PORT

— Port screen will open after 10 seconds with Slot Number 1, Port Number 1 displayed

— In the PORT window select the parameters specified in the Work Order

— PORT parameters are:

- Slot Number: AP1 - AP15 (e.g., choose AP1)

- Port: Port 1 - Port 32 (e.g., choose Port1)

- Service State: In-Service

- Startup Mode: Multimode, G.hs, or T1.413 (e.g., choose Multimode)

— In the ADSL Transmission Profile box choose one of the default profiles or a profile cre-ated previously

— In the PM Profile box, ADSL - select the profile “1-Default 1” for no ADSL PM TCAs, select “2-Default 2” for the default ADSL threshold crossings, SDSL - select the profile “127-Default 2” for the default SDSL threshold crossing, select “128-Default 1” for no SDSL PM TCAs or select a PM profile created previously

— Click Apply

— After about 20 seconds the Apply button will gray out.

— Repeat for all PORTs specified in the Work Order

32 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

H. FEEDER/SUBSCRIBER Cross-connects: If the Work Order specifies to create FEEDER and SUBSCRIBER cross-connections perform the following steps:

NOTE:For QoS functionality, the Minimum Bit Rate in the xDSL Transmission profile for the port must be greater than or equal to the Peak Cell Rate (PCR) for CBR or Sustained Cell Rate (SCR) for rt-VBR/nrt-VBR in the ATM traffic profile associated with the cross-connect for the port. Information on QoS is provided in Appendix 12 on page 40.

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab) Cross Connect

— In the Feeder window select the parameters specified in the Work Order

— Click on each box to select

— For FEEDER parameters (set according to the switch):

- VPI: (e.g., 5) - valid range = 1 - 255 (1 - 243 for VP-only cross-connect) - ifVP-only cross-connect, this not one of the Shelf VPs

- VCI: (e.g., 33) - valid range = 33 - 1999 - if VP-only cross-connect, VCI blank

— For SUBSCRIBER parameters (set according to mode/type of modem):

- Slot Number:AP1 - AP15 (e.g., choose AP1)

- Port:PORT1 - PORT32 (e.g., choose Port1)

- VPI: (Provided in the Work Order, e.g. use 0 for bridged mode with 3COM modem) - valid range = 0 - 255

- VCI: (Provided in the Work Order, e.g. use 33 for bridged mode with 3COM modem) - valid range = 0 - 1999

— For ATM Traffic Profile, select from the list in the Profile box

— If the Work Order specifies identifier for the cross-connect, enter text in the optional Circuit ID box

— Click Connect

— Repeat for all cross-connects specified in the Work Order

— When all the cross-connects have been created, verify that they are correct by clicking “View All Cross Connects” and reviewing the information

— When done reviewing cross-connects, hit Cancel to close screen

13. Installation of ADSL or SDSL AP packs

NOTE:Software Download Status indication (LED) When an ADSL AP is software downloaded, the software download complete event appears before the ADSL AP Fault LED stops blinking.

A. Locate the AP slot specified in the Work Order

33 of 50





1---5----10----15----20----25----30----35----40----45---

B. Remove the tip/ring cable from cable holder panel and remove the cable holder panel

C. Plug-in the AP pack into the AP slot

— Verify on pack insertion that the LED blinks for 5 - 30 seconds (LED is lit steady for 10 sec-onds on LPS716 AP) on a pack with software on it (about 5 minutes for one with no software), then the light goes out. If the Fault LED remains lit, there could be a non-service affecting fail-ure. Remove and reinsert the AP. Wait until the LED has stopped blinking. If the LED still is lit, consult the Alarms section of the AnyMedia Access System Commands and Procedures for Data Services Manual.

D. There will be a Major (MJ) alarm displayed on the AFM pack

E. Connect tip/ring cable to the AP pack. Major alarm clears

F. To verify Pack status at GSI, go to View ==> Data Status

G. Select Pack (e.g., AP-1). Slot Operational Status should be Equipped, Pack Operational Status should be In Service. If not, wait 5 minutes and repeat

H. If AP not reported In Service, remove pack then re-insert. Wait 5 more minutes, then check Pack/Port status as above.

14. Modem Connection

A. Connect modems to provisioned ports on AP. Wait few minutes for modem train-up. Note, SDSL ports may take up to 30 minutes to go in-service.

B. To verify Port status at GSI, go to View ==> Data Status

C. Select Pack (e.g., AP-1) and Port (e.g., Port1)

— Port status and Transmission Conditions will be reported within 1 minute

! WARNING:If SDSL modem fails to train-up, check for correct polarity on Tip/Ring cable

D. If the AP is reported In Service but the Port Operational Status is Out of Service, verify that the con-nection to the modem is correct. If it is correct, attempt to bring the port into service by toggling the port. This is done by the following procedure:

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab) PORT

— In the PORT window select the parameters specified in the Work Order

— For PORT parameters:

- Slot Number: AP1 - AP15, Select the affected pack

- Port: Port 1 - Port 16, Select the affected port

- Service State: Out of Service

— Click Apply.

— Repeat Port provisioning setting port In Service as follows:

34 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— For PORT parameters:

- Slot Number: AP1 - AP15, Select the affected pack

- Port: Port 1 - Port 32, Select the affected port

- Service State: In Service

— Click Apply.

— Wait 5 minutes. Retrieve PACK/PORT status as described above. If the PORT status is still Out of Service, Power Cycle the modem. Wait 5 minutes. Retrieve PACK/PORT status. The PORT status should now be In Service

— Repeat for all modems on pack

15. Checking system is free of alarms

A. If Active Alarms screen is open, check for alarms. If not, hit Retrieve/Show Alarms icon on Menu bar or select Fault ==> Alarms. There should be no active alarms displayed. If any alarms appear, con-sult the Alarms section of the AnyMedia Access System Commands and Procedures for Data Ser-vices Manual for information on clearing the alarms.

35 of 50


8. Operational and Maintenance Procedures Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

8. Operational and Maintenance Procedures

This section contains procedures to perform normal operational or maintenance actions.

! WARNING:When removing or inserting a pack, always wait 15 seconds before removing or inserting the same or another pack.

1. Growth of an ADSL or SDSL AP pack

A. Provision the AP slot/ports as per above procedures

B. Locate the AP slot specified in the Work Order

C. Remove the tip/ring cable from cable holder panel and remove the cable holder panel

D. Plug-in the appropriate AP pack type into the AP slot

— Verify on pack insertion the FAULT LED lights momentarily

— Wait at least 5 minutes and verify that all pack LEDs are OFF

E. Connect tip/ring cable to the AP pack. Alarm for Tip/Ring Cable disconnect will clear

2. Degrowth of an ADSL or SDSL AP pack

A. From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab) PACK

— In the Pack window select the parameters specified in the Work Order

— Pack parameters are:

— Slot Number: AP1 - AP15 (e.g., AP1)

— Pack Type: ADSL or SDSL

— Configured State: Out of Service

— Click Apply

— After about 40 seconds, Apply button will gray out.

— In the Pack window, delete the Out of Service pack by hitting Delete

— After about 40 seconds, confirmation message appears. Click OK in confirma-tion box

B. Disconnect tip/ring cable from AP specified in the Work Order

C. Remove AP pack specified in the Work Order

D. Insert cable holder panel into AP slot and insert tip/ring cable into panel

E. Major (MJ) alarm will be reported for AP Pack Removal. This alarm may be cleared by selecting the alarm in the GSI Alarm screen (click on “mj” at left), then hit Clear BB Alarm

F. If system is equipped with a COMDAC, clear pack missing alarm at COMDAC using ED-CONFIG command:

— From menu bar select TL1 COMMANDS ==> ALL COMMANDS ==> ED ==> CONFIG

36 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 8. Operational and Maintenance Procedures

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— In the ED-CONFIG window select: AP-1-{slot # pack removed from} and NR (not required)

— Hit YES when ask to confirm command

3. Migration of AP packs

To change a slot equipped with a 4-line AP pack (e.g., LPA400B) to a 8-line LPA408 AP:

A. Remove the existing AP and insert the 408 AP. In Logical Port Mode, Ports 1-4 (if previously provisioned for service) will recover. In Physical Port Mode, Ports 1, 3, 5, and 7 (if provisioned for service) will recover.

B. If specified in the service order, provision Ports 5-8 (Logical Port Mode) or Ports 9, 11, 13, and 15 (Physical Port Mode). Use procedures from Section 6

To change a slot equipped with an 8-line LPA408 AP to a 4-line AP, ports 5-8 (Logical Port Mode) or ports 9, 11, 13, and 15 (Physical Port Mode) must be deleted (if provisioned)

A. From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab)PORT

B. Port screen will open after 10 seconds with Slot Number 1, Port Number 1 displayed

C. In the PORT window select the parameters for port being deleted

— PORT parameters are:

- Slot Number: AP1 - AP15 (e.g., choose AP1)

- Port: Port 1 - Port 32 (e.g., choose Port5)

- Service State: Out of Service

D. Click Apply.

E. To delete the OOS port, hit Delete Port. Click Yes at Confirmation

F. Repeat for other ports requiring deletion

G. Remove the LPA408 AP and insert the new AP. Ports provisioned for service will recover

4. Determining operational status of ADSL or SDSL AP pack and ports

A. From the menu bar select View ==> Data Status

B. Enter AP slot number in Pack field

C. Verify pack operational status of the added AP pack is In Service

D. Enter Port number in Port field

E. Verify port operational status of the added port is In Service

F. Observe SNR Margin, Attenuation, and Transmit Rate is reported in Upstream and Downstream directions

G. Repeat for each port/pack

37 of 50





1---5----10----15----20----25----30----35----40----45---

5. Downloading AFM Software

! WARNING:During software download, the AFM does not respond/responds slowly to commands (e.g., blank screen is displayed after GSI logon from another PC)

! WARNING:You must use 2.2.1 or 1.4.18 GSI to download any 1.11.x software

A. Check that you are running GSI 2.2.1-123 or 1.4.18 B158 from the about GSI tab. Update the GSI if you are running an earlier version. Note: Remove the old GSI before installation of the new one - refer to procedures in Section 9.

B. Obtain a CD-ROM with the correct AFM software, R1.11.1.2

C. Follow directions with the CD-ROM to download the software into a directory on the PC

D. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Download

E. In the “Download Software From” box, browse to the directory with the software load

F. Double-click on the “version.txt” file. Verify that the software version is correct in the Selected SW Version box. The second line should say LPA900 R1.11.1.2

G. Click on the Download Only button and click OK to begin the Software Download. The software download will take approximately 45 minutes (slower if download via Console port).

H. At the GSI, an FTP window will appear with a progress bar. At bottom of screen, “FTP In Progress” is displayed. When the progress bar is completed and window closes, the software download is com-plete. “No Reboot Required” will be displayed at bottom.

6. Activate AFM Software

A. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Activate

B. Verify that the software load listed in the box labeled Version Available for Activation is the software desired

C. Click on the Activate Software button. Activate window stays open, and Progress bar opens at bot-tom of display with message “Awaiting Software Activation”. Activation should take about 10 minutes. When the Activation is complete, the Activate window closes and “Software Activation Complete”message is reported at bottom of display.

D. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Activate

E. Verify the new software load is reported in the Version Active After Next Reboot box. Hit Cancel

7. To reboot the system:

2.2.1 GSI: From the menu bar select NE Operations ==> AFM Reboot

1.4.18 GSI: From the menu bar select NE Operations ==> SW Download ==> AFM Reboot

— If hard reset is required (service-affecting), click the Hard Reset box

38 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— In the Reboot window, click Reboot Now. Reboot window stays open, and Progress bar opens at bottom of display with message “Reboot In Progress”.

— All LEDs on the AFM pack come on for a few seconds. During initialization, the AFM FAULT LED blinks at a 1 per second rate

— When initialization has completed, the AFM ACTV LED will remain on. Initialization takes approximately 10 minutes.

— After about 2 minutes, Reboot window closes and the Connect Window will appear. Put the Security ID “public” (or as provisioned) in the Connect To Shelf window and click connect

8. Setting up an In-Band Management Channel

! WARNING:RFC1483 routed encapsulation LLC snap is required on the network side in order to commu-nicate with the in-band management channel on the AFM. Neither a Bridge Router nor a Pro-tocol Converter such as the AC-60 or SA-600 can be used.

! WARNING:If AFM has been upgraded from R1.1.2 or R1.4, the In-Band Management Channel is set with Service Class of UBR if the In-Band Channel VP is a Shelf VP (Service Class will be rtVbr if In-Band Channel VP is not a Shelf VP). If In-Band Management Channel is set up in R1.7.3.3 or R1.11, it has a Service Class of rtVbr. The network side MUST be set up with same Service Class for the In-Band Management Channel to function. Note, the Service Class for the In-Band Channel is reported in the System VP Entries report (Select Provisioning ==> Equip-ment ==> System VP Entries).

A. Create the Network Module and configure the Network Management System at network side.

B. To set the Operations Channel VPI/VCI:

— From menu bar select Provisioning ==>System Turnup ==> Data ==> Main Shelf ==> (Tab) Main Shelf

— Click Global ATM Parameters tab

— Enter the ATM Operations Channel VPI and VCI specified in the Work Order. Note, the Operations Channel VPI does not have to be the same as the Shelf VPI.

— Click Apply.

C. Determine an IP address for the AFM ATM Operations Channel (and COMDAC if the In-Band Management Channel will be used for access to the COMDAC. The AFM and COMDAC10Base-T port addresses should be in the same subnet).

D. Using local access, log into the AFM and provision the AFM communication parameters.

— From the menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab) Communications

39 of 50





1---5----10----15----20----25----30----35----40----45---

— In the IP configuration text box enter the ATM IP address previously determined and note it for reference. Select ATM. A dot appears next to ATM and the Default Router should be grayed out.

— At the bottom of the screen, click on OK. This runs for about 90 seconds.

E. If the In-Band Management Channel is to be used for the COMDAC, log into the COMDAC using local access and provision the IP address.

— Use SET-IP command to set IP address and Default Router. The IP address should be on same subnet as the AFM. The default Router must be the AFM 10BaseT IP address.

F. Connect a crossover 9-pin, 10Base-T cable from the AFM to the LAN port of the system.

! WARNING:Clear all interface alarms before attempting to access the AFM or COMDAC.

G. Both the AFM and the COMDAC can now be accessed through the In-Band Channel.

9. Changing ADSL/SDSL Transmission Profile on a Port

! WARNING:When changing ADSL transmission profile for a port, the cross-connect must be deleted and a new cross-connect created. This is accomplished automatically when the port is deleted.

To change the profile assigned to a port, first retrieve the cross-connect information for that port, set the port to OOS, delete the port, set the port in-service with a new profile number, then provision the cross-connect(s).

A. Retrieve the cross-connect for the port

— From the menu bar, select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab) CrossConnect

— Hit View All Cross Connects to get the parameters

— Note which cross connects are assigned to the port.

B. Change port to OOS and delete the port

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (Tab)PORT

— Select Slot Number and Port

— Set Service State to Out of Service

— Click Apply.

— To delete the port, click Delete port

C. Reprovision the port using the new profile number

40 of 50




1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— In Port screen, select new Transmission Profile number from pull-down list (if a new profile is needed, use procedure from Section 6 - Item 12 to create profiles)

— Set Service State for Port to In-Service

— Select Startup Mode

— Select Performance Monitoring Profile

— Click Apply.

D. Re-enter the cross-connect for the port

— From menu bar select Provisioning ==> System Turnup ==> Data ==> Main Shelf ==> (tab)Cross Connect

— Enter Feeder and Subscriber parameters for the port

— Hit Connect.

41 of 50


9. Software Upgrade Procedures Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

9. Software Upgrade Procedures

This section describes the recommended steps to convert a system running any previous release to Release 1.11.1.2. Before download of new software, the GSI must be upgraded.

! WARNING:The GSI must be upgraded to version 2.2.1-B123 or 1.4.18 B158 before downloading R1.11.1.2 software. This GSI MUST be used only for Download/Activate/Reboot.

! WARNING:Software Download may occasionally fail. If Download failure observed as indicated by FTP failure message or no load displayed in Version Available for Activation field in Activate screen, rerun the Software Download.

1. To upgrade the GSI:

— Always uninstall old GSI first. After downloading the GSI, create shortcut to the executable:

2.2.1-B123 GSI = C:\ProgramFiles\LucentTechnologies\AnyMedia\AMI-R2.2.1\gsiR2_2_1

1.4.18-B158 GSI = C:\ProgramFiles\AnyMedia\GSI\gsi.exe

2. Downloading AFM Software

! WARNING:During software download, the AFM responds slowly or does not respond at all to commands (e.g., blank screen is displayed after GSI logon from another PC).

A. Obtain a CD-ROM with the correct software, R1.11.1.2.

B. Follow directions with the CD-ROM to download the software into a directory on the PC.

C. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Download

D. In the “Download Software From” box, browse to the directory with the software load.

E. Double-click on the “version.txt” file. Verify that the software version is correct in the Selected SW Version box. The second line should say LPA900 R1.11.1.2

F. Click on the Download Only button and click OK to begin the Software Download. The software download will take approximately 45 minutes (slower via Console port)

G. At the GSI, an FTP window will appear with a progress bar. At bottom of screen, “FTP In Progress” is displayed. When the progress bar is completed and window closes, the software download is com-plete. “No Reboot Required” will be displayed at bottom.

3. Activate AFM Software

A. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Activate

42 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 9. Software Upgrade Procedures

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

B. Verify that the software load listed in the box labeled Version Available for Activation is the software desired.

C. Click on the Activate Software button. Activate window stays open, and Progress bar opens at bot-tom of display with message “Awaiting Software Activation”. Activation should take about 10 minutes. When the Activation is complete, the Activate window closes and “Software Activation Complete”message is reported at bottom of display.

D. From the menu bar, select NE Operations ==> Software (or SW Download) ==> Activate

E. Verify the new software load is reported in the Version Active After Next Reboot box. Hit Cancel

4. To reboot the system:

2.2.1 GSI: From the menu bar select NE Operations ==> AFM Reboot

1.4.18 GSI: From the menu bar select NE Operations ==> SW Download ==> AFM Reboot

— In the Reboot window, click Reboot Now. Reboot window stays open, and Progress bar opens at bottom of display with message “Reboot In Progress”.

— All LEDs on the AFM pack come on for a few seconds. During initialization, the AFM FAULT LED blinks at a 1 per second rate.

! WARNING:During this next step do not remove the AFM from the system - this pause is a normal step during the database evolution phase of the initialization.

— 5 minutes after the reboot all LEDs on the AFM will either go out or be lit for 5 minutes, then the AFM FAULT LED will blink again at a 1 per second rate.

— When initialization has completed, the AFM ACTV LED will remain on. Initialization takes approximately 15 minutes.

— Reboot window at GSI will close and Connect window will open

— The red LED on ADSL APs will blink while software is downloading

43 of 50


10. Appendix - ATM xDSL Port Numbering Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

10. Appendix - ATM xDSL Port Numbering

1. Overview

The AnyMedia Access System GSI uses port numbers for many activities related to ATM xDSL ports. These activities include the following:

• ATM xDSL port provisioning

• ATM cross-connect provisioning

• Status information retrieval

• Alarm and event retrieval.

Up to 32 ports can be provisioned for any given slot; however, if a given ATM xDSL AP is installed in a slot that has a port provisioned that the given AP does not have, then the operational state of the port will be MEA. For example, suppose Slot 4 were provisioned for a pack type of ADSL and Slot 4, Port 27 were provisioned for service. Then, if anLPA408 AP was installed in Slot 4, the operational state of Slot 4, Port 27 would be MEA, because port 27 is not connected on the LPA408.

2. Alternating and Sequential Pinouts

All of the ADSL APs described in Chapter 5 of the APOG, including the POTS/ADSL P4A4 AP, are examples of alternating pinout ATM xDSL APs. For this type of AP, the ATM xDSL signal appears on alternating tip/ring pairs on the faceplate connector, starting with Pair 1 (that is, Pairs 1, 3, 5, 7, and so forth). On ADSL-only APs like the LPA408 AP, the even-numbered pairs are for the connection to the incoming POTS signal.

The SDSL16 AP is an example of a sequential pinout ATM xDSL AP. For this type of AP, the ATM xDSL signal appears on sequential tip/ring pairs on the faceplate connector, starting with Pair 1 (that is Pairs 1, 2, 3, 4, and so forth)

3. Port Numbering Modes

Two port numbering modes are provided. These modes determine what port numbers are used for the GSI activities listed above. The modes are:

• Physical—A port number entry on the GSI corresponds to the identification number of the tip/ring pair on the AP faceplate connector that provides the service. This mode is similar to traditional telephony operations in which the pack pair number is part of the TL1 AID for a drop.

• Logical—Port entries on the GSI are numbered contiguously from 1 to n independent of the order in which they appear on the AP faceplate connector. Earlier releases of the AnyMedia Access System ATM xDSL port operations used this mode. (see examples in Table 1, on page 44)

For alternating pinout ATM xDSL APs, the GSI port number entries that correspond to the tip/ring pairs that provide the service depend on which port numbering mode is in effect. This behavior is caused by the skipped tip/ring pairs. On the other hand, for sequential pinout ATM xDSL APs, the GSI port number entries that correspond to the tip/ring pairs that provide the service are the same regardless of the port numbering mode.

44 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 10. Appendix - ATM xDSL Port Numbering

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

The default setting of the port numbering mode is physical. However, if the AFM software is updated from a release that provides only the logical port numbering mode to a release that provides both modes, then the setting will automatically be set to logical. That way, the mode does not change as a result of the software-update activity.

When the port numbering mode for an in-service system is provisioned to a different value, the AFM will reboot but end-user transmission is not affected. Furthermore, the port numbers entered and observed on the GSI automatically begin to follow the new mode. As a result, system administrators need to update line records to reflect the new port numbering mode whenever the port numbering mode is changed.

4. Examples

An example using the LPA408 AP, an alternating pinout AP, is given in Table 1 below.

So, if, for example, ADSL service (and POTS if applicable) is needed on AP Pair 5 on an LPA408 AP, then the port number used on the GSI for each mode is:

• Physical: Port 5

• Logical: Port 3.

• However, for the SDSL16 AP, a sequential pinout AP, the tip/ring pairs that provide service are Pairs 1, 2, 3, and so forth up to and including 16. In this case, the port number used on the GSI is the same regardless of the port numbering mode.

Table 1. LPA408 AP Port Numbering

AP Tip/Ring Pair Number

Port Number Entered or Observed on GSI

Physical Mode Logical Mode

1 1 1

3 3 2

5 5 3

7 7 4

9 9 5

11 11 6

13 13 7

15 15 8

45 of 50


11. Appendix - GSI PPP Activation Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

11. Appendix - GSI PPP Activation

1. Requirements for GSI PPP services:

A. NT 4.0 platform

• NT 4.0 Service Pack 4 or later

• Download the latest NT service packs from:

http://www.microsoft.com/ntserver/nts/downloads/default.asp

B. For WIN 95:

• Install Microsoft Dialup Networking 1.3 or later

• DUN13.exe can be found in the GSI directory and is distributed with the GSI

C. For WIN 98 and 2000, and the above platforms

• Install the GSI 2.2.1

2. Service Activation on the PC:

To activate the PPP support for the GSI requires the following to be installed the first time on your system:

NOTE:Windows NT4.0 Security does not allow the automatic/programmatic installation of these com-ponents without the involvement of User/Administrator of the system. This is the reason the GSI installation program does not complete these steps automatically.

1. Install a modem-like device which will support the serial connection between the GSI and the COMDAC/AFM. This device file has been copied to your system by the GSI installation.

• At PC, from Control Panel, click on Modems.

• Click “Add”, then select “Don’t detect my modem” and click “Next”

• Select “AnyMedia GSI” and “PPP Connection”

• Select COM1 and click “Next”, then click ‘Finish”

• On Modem window, select “Properties”.

• Select Maximum speed: 19200, then click Connection tab

• Verify settings “8, None, 1” then click Advanced

• Verify “Use flow control” should be off, click on “Record a log file”, click OK

2. For NT 4.0 and WIN 2000, must Install/Activate the Remote Access Service if not already installed in your system

• At PC, from Control Panel, click on Network

• If Remote Access Service does not appear in the list, click “Add”

46 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 11. Appendix - GSI PPP Activation

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

— Select “Remote Access Service” and click OK. Restart system if prompted

• If Remote Access Service appears in list, select it and click “Properties”

• If “PPP Connection” appears in list, click Cancel because the Connection exists. Otherwise, click “Add”

• If the “PPP Device” is already installed, it will appear in list of “RAS Capable Devices”. Select it and click OK. Otherwise, click “Install Modem” and run procedure in step 1 above.

47 of 50


12. Appendix - QoS/Connection Admission Control Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

12. Appendix - QoS/Connection Admission Control

Connection Admission Control (CAC) determines if a requested connection can be provisioned with assurance that the service can be provided. UBR connections are always accepted by the CAC.

Three parameters determine the shelf capacity used in the CAC algorithm: Shelf PCR, the Minimum Bit Rate of the subscriber interface, and the Shelf Overbooking Factors.

The Shelf Peak Cell Rate (PCR) is the maximum bandwidth in cells per second a shelf can guaran-tee. In a single shelf system, this value can be the default, which is also the maximum, i. e., the full bandwidth of the feeder interface to the ATM network. When the Shelf PCR is lower than the feeder bandwidth, the remaining bandwidth can still be used by Unspecified Bit Rate (UBR) traffic. (In fact, UBR traffic can use any bandwidth not currently in use by other connections with more stringent QoS.) One value specifies the upstream rate and one value specifies the downstream rate.

The Minimum Bit Rate (upstream and downstream) specified in the transmission profile is the mini-mum rate at which the link (ADSL or SDSL) will train. The customer loop qualification tests should give a good indication of this value.

This Minimum Bit Rate is used in determining whether a new connection can be admitted to the shelf. For a CBR, VBR or nrt-VBR connection, the Minimum Bit Rate (both upstream and downstream) must be able to support the PCR for CBR connections or SCR for VBR connections as well as any existing connections.

An approximate conversion factor that can be used in this calculation is:

2.5 Minimum Bit Rate in kilobits per sec. (kbps) = PCR/Shelf Overbooking Factor (cells per sec.)

A transmission profile is applied to a port during port provisioning. Note that the creation of the profile and the port provisioning may be accepted, but a connection using the profile may be rejected. The parameters must be chosen to be compatible with the planned service and the modem to be used.

The Shelf Overbooking Factor is a measure of the level of statistical multiplexing in the system. This factor multiplies the Shelf PCR and the Minimum Bit Rate when the CAC determines if a new connec-tion can be admitted to the shelf. Separate factors apply to the four service classes: Constant Bit Rate (CBR), real time Variable Bit Rate (rt-VBR), non-real time VBR (nrt-VBR) and UBR. An example of how this parameter functions is as follows:

When the overbooking factor for CBR, nrt-VBR and rt-VBR is 2, connections will be accepted until one of these conditions fails:

1. The total bandwidth required [sum of all PCRs (for CBR connections) and all SCRs (for VBR connections)] by these connections does not exceed twice the shelf PCR and

48 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 12. Appendix - QoS/Connection Admission Control

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

2. The total bandwidth required [sum of all PCRs (for CBR connections) and all SCRs (for VBR connections)] by all connections on a subscriber line does not exceed twice the Minimum Bit Rate of the port.

The larger the Shelf Overbooking Factor, the better the network is utilized but the greater the risk for congestion, which may result in cells to be dropped. The values selected for the overbooking factor may need to be tuned after monitoring the ATM Traffic statistics. If congestion is being encountered too frequently, provisioning needs to be adjusted to relieve it.

If congestion is localized to a port, increasing the Minimum Bit Rate of the port can provide more bandwidth for those connections. All cross connects on a port must be deleted before changing any parameters in the port profile. It is recommended that a new port profile be created with the new parameters, since the profile may be in use on other ports. Once the port is provisioned with the new profile, the cross connects can be re-created.

If congestion is general to the shelf, it may be desirable to reduce the Shelf Overbooking Factors. Reduction of an overbooking factor will be rejected if it is reduced below the level needed to accom-modate existing connections. In this case, connections may need to be moved to a new line, possibly a new shelf before the overbooking factor can be reduced.

49 of 50


13. Glossary Issue 5, July 2001



1---5----10----15----20----25----30----35----40----45---

13. Glossary

ADSL Asymmetric Digital Subscriber LineAEM AnyMedia Element ManagerAFM ATM Feeder MultiplexerAOS-BB AnyMedia Access System Operations Software for Broadband ServicesAP Application PackATM Asynchronous Transfer ModeBAIU Broadband Access Interface UnitCAC Connection Admission ControlCBR Constant Bit RateCDVT Cell Delay Variation ToleranceCOMDAC Common Data And Control PackCPE Customer Premises EquipmentDMT Discrete Multi-ToneDS3 Digital Signal Level ThreeE3 European Digital Signal Level ThreeFAST Flexible Access Subscriber TerminalFCM Fuse Control ModuleFTP File Transfer ProtocolGSI Graphical System InterfaceHBER High Bit Error RateIMA Inverse Multiplexing over ATMISDN Integrated Services Digital NetworkLOS Loss Of SignalMEA Mismatch of Equipment and AttributesNVDS Non-Volatile Data StorageOAP Optical Application PackOCP Optical Controller PackONU Optical Network UnitPCR Peak Cell RatePOTS Plain Old Telephone ServicePPP Point-to-Point ProtocolQoS Quality of ServiceR&R Remove and ResetSDSL Symmetric Digital Subscriber LineSNR Signal-to-Noise RatioTCA Threshold Crossing AlertUBR Unspecified Bit RateVBR Variable Bit RateVCI Virtual Channel IdentifierVPI Virtual Path Identifier

50 of 50



363-211-158AnyMedia Access System: Software Release Description, R1.11.1.2Issue 5, July 2001 13. Glossary

1---5----

10----

15----

20----

25----

30----

35----

40----

45---

Documents

AnyMedia Access System Operations Software for · PDF fileIssue5 July 2001 1 of 50 LUCENT ... 018, 020, 026, 029, 031, 40), R1.11.0.1- ... • F5 AIS • Dying Gasp event on xDSL link