[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2563.0. "Deleting a single protocol entry???" by CSC32::WOESTEMEYER (Why??...Why not!!!) Fri Mar 13 1992 16:12

    Using DECmcc V1.1.0 and ELM Bridge AM on a DECbridge 620 I have entered
    a list of protocol entries to be filtered:
    
    Create bridge db620_1 prot data ether entry xx-xx dispos filter
    
    This works fine and can be displayed as well.  Now the problem, if a
    single entry neededs to be deleted:
    
    Delete bridge db620_1 prot data ether entry xx-xx 
    
    The result is:
    
    Execution of requested operation failed at target entity
    
    This bridge has no password set up on it.  This would seem to be a
    problem with V1.2 as T1.2.4 works as expected.  This is fine for me
    however, this is really a customer problem and he does not have field
    test software.  Is there any way to delete a single entry in the
    existing released version??
    
    Steve Woestemeyer
    CSC/CS - Network Support Team
    
     
T.RTitleUserPersonal
Name
DateLines
2563.1QUIVER::CHILDSEd ChildsTue Mar 17 1992 11:1627
| Delete bridge db620_1 prot data ether entry xx-xx
| The result is:
| Execution of requested operation failed at target entity

    This is a bug with the V1.2.0 Bridge AM.  The DECbridge 600 Series uses
    a different RBMS code to delete protocol entries than do the other
    bridge models.  This problem does not occur with the 200 or 500 series
    bridges.  This problem has been fixed in the T1.2.4 ELM kit.

| Is there any way to delete a single entry in the
| existing released version??

    No there isn't unfortunately.  Use RESET PROTOCOL DATABASE to delete
    all of the entries, and then CREATE the correct ones.  Customers
    typically only have a small handful of protocol filters, so this
    probably won't be that painful a workaround.  You can also use the
    following commands:

    	SHOW BRIDGE <bridge-id> PROTOCOL DATABASE ETHERNET ENTRY * ALL CHAR
    	SHOW BRIDGE <bridge-id> PROTOCOL DATABASE SAP ENTRY * ALL CHAR
    	SHOW BRIDGE <bridge-id> PROTOCOL DATABASE SNAP ENTRY * ALL CHAR

    to show all the entries you have.  Put the output in a COM file and
    edit in some CREATE BRIDGE <bridge-id> PROTOCOL DATABASE ETHERNET ENTRY
    aa-bb commands to re-create the filters.

    Sorry for the inconvenience.