Software Increment Release Notes
================================

Increment ID:   I28A1730
Date created:   April 04, 2001


Title: 
------
VLCM Fix Bundle and Message Waiting for the UE9k


Effect on Traffic:
------------------
This increment has no effect on traffic.


Detailed Description of Increment:  
----------------------------------

1.) Corrects a resetting message waiting queue condition.  Support for
    UE shelf card types (4+4, 8+8, and 10+10 ADSL/POTS line cards) have
    been added to allow the message waiting option to work properly on
    these ADSL card types.

2.) Enhance 2nd VLCM event reporting.  Line Card state reporting is
    not being received correctly on a second VLCM.  The problem is
    that the lsg is not being calculated correctly.  This update
    changes the way the lsg is calculated.

3.) This increment will allow customers with a DMS10 with two VLCMs to
    provison as a single site (only one RMM).  Previously, this
    configuration would not work since the VLCM code couldn't identify
    which VLCM was carrying the test session and checks in the code were
    preventing VLCM messages from being accepted.  This patch removes
    those checks, allowing the VLCM messages to come from the DMS10 without
    being rejected, regardless of the VLCM configuration.

4.) Fixes a procedure in which a NIL host ID causes a software trap when
    performing any TL1 command that retrieves the hostname for a VLCM line.
    A check is now performed prior to accessing the host data table to
    prevent this.


System Configuration / Shelf Type Requirements:
-----------------------------------------------
This increment is applicable to all AN17.30 AccessNode configurations,
shelf types, and interfaces.


Prerequisite Increments Required:
---------------------------------
Increments I01A1730 through I27A1730 must be successfully applied prior to 
application of this increment.


Loads Affected:
---------------
APU: ACCL17AS


Special Instructions:
---------------------
NONE


Installation Instructions:
--------------------------
Please refer to the Incremental Software Delivery Users Guide for general 
installation instructions.  This document may be obtained from either the 
AccessWeb ISD web site (https://www23.nortelnetworks.com/ACCESS_OPTICAL/esd/),
where the AccessNode increments are located, or you may order it through your 
Nortel Account Manager or Order Manager.  The document number for the 
Incremental Software Delivery Users Guide is P0934362.


Test Instructions:
------------------

For issue #1:
 
 1) Establish a line with the MWT (message waiting) option.
 
     Example:  ado $ 2290769 mwt cmwi y y act y no n $ yy
               ado $ 2290770 mwt cmwi y y act y no n $ yy
        
 2) Queue a message onto the message waiting queue for the line established
    in step 1 above using the MWQ command.
    
     Example:  mwq queue 2290769 l 2290770
     
 3) Reset the message queue, again using the MWQ command.
      
     Example:  mwq reset 2290769

 4) Verify that no SWER logs have been generated.
 

For issue #2:
 
 1) Gain access to the DMS-10 interface

 2) Make sure a line is provisioned on VLCM 2

 3) Get into the PED overlay: 'ovly ped imed'

 4) Start a test session on the provisiond line:
    'test lpk neXX lce <bay> <shelf> <lsg> <line>'

 5) Make sure the result is "PASSED"

 
For issue #3:
 
 A new CI command, "SNGLRMM" has been included for those customers who
 are running dual VLCM's with a single RMM.  The parameters for this command
 are "on" and "off", and can be performed at the NEUI or CI level.
 
  Example:

   > snglrmm on   (this command enables support for dual VLCM with a single RMM)
   or:
   > snglrmm off  (this command disables support for dual VLCM with a single
                   RMM.  Note: "off" is the default setting, which minimizes
                   customer impact for those supporting more than one RMM.)

 After applying the patch, take a line off the 2nd VLCM out of service from the
 Network Element's eq lc or eq anxlc screen.  At the DMS-10, check for a PED737
 message, and verify the same line is in a busy status.  From the NE, place
 the line back in service.  A PED738 message should be received by the DMS-10,
 and the line should be in an in service state.


For issue #4:

 Testing not required.