Conference noted::atm

813.0. "deletion of ABR pt-to-mpt branch?" by LEMAN::MAEUSLI () Fri Jan 31 1997 08:36

One of our customers has created a pt-to-mpt ABR circuit (in the VOLATILE 
memory) and is asking us how to delete one of the branches of the above ABR 
pt-to-mpt VC circuit, WITHOUT to delete the root and all its associated 
branches.

I've had a look into the OBM menu of the GS/ATM V2.1.1 (Rom:V351,App:V356) and
apparently there is no option provided with the menu (see below) to handle the
deletion of a single ABR branch from the VOLATILE memory:

	>                 2.3 Virtual Circuit Delete Menu
	>
	>        1. Remove Point-to-Point VC
	>        2. Remove ABR Point-to-Multipoint VC Circuit
	>        3. Remove CBR Point-to-Multipoint VC Circuit
	>        4. Remove CBR Point-to-Multipoint Branch VC
	>        5. Remove PVC Record from flash only
	>        6. Unbind VC Range in volatile memory
	>        7. Return to Virtual Circuit Menu
	>

I've tried several options with the following results:

   option 4: (Remove CBR Point-to-Multipoint Branch VC): --> refuse to
                     execute the command because this is a ABR pt-to-mpt
                     branch.

   option 2: (Remove ABR Point-to-Multipoint VC Circuit): --> delete
                     the ABR pt-to-mpt root and ALL its branches.

   option 1: (Remove Point-to-Point VC): --> by specifying the outvci#
                     of the ABR branch as the invci# at the prompt of this
                     option, the ABR branch seems apparently to be deleted.

Questions: - why isn't there any explicit option in the menu 2.3 to remove an 
*********    ABR branch from the VOLATILE memory (whereas there is one in the 
             equivalent menu (menu 2.3.5: Flash VC Record Delete Menu)?

           - is option 1 of menu 2.3 (see above) a temporary work-around to 
             solve this problem (I'm not sure that the VC internal structures
             are cleanly managed by using this way)?

           - is an IPMT needed for that, in order that correctives actions be 
             taken?

Thank's in advance for clarifying the above issue. 

      Charles

I don't know why that's the case.  I'll ask someone who knows the "internals"
of circuit setup about this, to see if there's a reason why this was left off
or if it was just an omission on the part of the OBM menu developer.