[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

5363.0. "Filtering on a port" by SUBURB::MORGANP () Tue Jul 20 1993 14:12

    Hello,
    
    	Could someone please tell me the correct syntax for creating
    	a filter on a port on a Decbridge. I can create a filter for
    	a physical address on the whole bridge but can't seem to find
    	the command for the same result on just a single port on the
    	bridge, thank you
    
    
    
    				Paul
    
    
    	p.s. the command I use for the whole bridge is:
    	create bridge 'bridge-name' forw data stat entry 'physical addr'
    	disp=filter by password= 'password'
T.RTitleUserPersonal
Name		DateLines
5363.1Filtering on DECBridge 600 seriesRDGENG::GREIDSo Far. So Good, So What ?Thu Oct 14 1993 08:1734
    Further to note 5363 that a colleague of mine entered some time ago,
    regarding filtering on protocol or multicast addresses on DECBridge
    600s, I have recently been able to set-up filters on one port on a
    DECbridge 620 for 60-07,08-00 and ab-00-00-01-00-00. However I cannot
    seem to be able to filter the above on two or all three AUI ports, only 
    one. I have spent ages trying different syntax for the same command
    below but without success. Does anyone know the correct method for 
    setting up a filter on more than one AUI port ?
    
    MCC> CREATE BRIDGE Bridgename FORW DATA MULTI ENTRY AB-00-00-01-00-00
    	FILTER PORTS=[2]
    				__ Creates a filter for MOP and sets the 
    				   filter on AUI port 2
    
    However :
    
    MCC> SET BRIDGE Bridgename FORW DATA MULTI ENTRY AB-00-00-01-00-00
        FILTER PORTS=([2,][3,][4])
    
    				-- This is taken from the appropriate
    				chapter of the MCC Bridging manual for 
    				filtering on more than one port, the
    				command fails with :-
    
    %MCC-I-NOPARCMD, ([2,][3,][4])
                     ^
    %MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
    %MCC-E-SPLIT_CONSLIST, error in list of values
    
    ------------------------------------------------------------------------
    
    Thanks,
    
    Giles.
5363.2Try it without the square bracketsMOLAR::MOLAR::BRIENENNetwork Management Applications!Thu Oct 14 1993 09:3829
REL 5363.1

>    MCC> SET BRIDGE Bridgename FORW DATA MULTI ENTRY AB-00-00-01-00-00
>        FILTER PORTS=([2,][3,][4])
>    
>    				-- This is taken from the appropriate
>    				chapter of the MCC Bridging manual for 
>    				filtering on more than one port, the
>    				command fails with :-
>    
>    %MCC-I-NOPARCMD, ([2,][3,][4])
>                     ^
>    %MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
>    %MCC-E-SPLIT_CONSLIST, error in list of values


   The command format given in the Bridge Access Module Users Guide is
   a little confusing.  I believe the problem is that square brackets
   are supposed to indicate something is optional...

   Other examples in the User's Guide (as opposed to pages showing command 
   format) suggest the command should look like:

     MCC> SET BRIDGE Bridgename FORW DATA MULTI ENTRY AB-00-00-01-00-00
	  FILTER PORTS = (2,3,4)

   Have you tried the command without the square brackets?

							Chris
5363.3Applying filters RDGENG::GREIDSo Far. So Good, So What ?Thu Oct 14 1993 10:3813
    Chris,
    
    	Thanks for the suggestion, yeah I treid all sorts of combinations
    of brackets and spacing and commas but couldn't get it to accept any
    of them. The format you suggests generates the error :-
    
    %MCC-E-NOPARAMLIST, no parameter list was supplied in this ILV buffer
    
    	If you can think of anything else please post it.
    
    	Cheers,
    
    	Giles.
5363.4Inbound/Outbound filteringRDGENG::GREIDSo Far. So Good, So What ?Thu Oct 14 1993 11:2443
    I have managed to progress somewhat with this filtering problem.
    
    If for example I wish to filter MOP (AB-00-00-01-00-00) from the AUI
    ports 2,3 and 4, I can issue the following :-
    
    MCC> set bridge Bridgename forw data multi entry ab-00-00-01-00-00 -
    _MCC> Filter Map = ( (inbound port = 2, outbound ports (1,3,4)), -
    _MCC> (inbound port = 3, outbound ports (1,2,4)), -
    _MCC> (inbound port = 4, outbound ports (1,2,3)) )
    
    This returns the following :-
    
    Modification completed successfully.
                                Forward Map = ( (
                                   inbound port = 1,
                                 outbound ports = ( 2,
                                                    3,
                                                    4 ) ) )
    
    MCC>
    
    This I would take to mean that the Bridge will pass a MOP packet from 
    the FDDI port out to the AUI ports but not vice versa or one AUI port
    to another.
    
    However if I issue :-
    
    MCC> set bridge 7-b610-swrm-a forw data multi entry ab-00-00-01-00-00 -
    _MCC> Filter Map = ( (inbound port = 1, outbound ports (2,3,4)), -
    _MCC> (inbound port = 2, outbound ports (1,3,4)), -
    _MCC> (inbound port = 3, outbound ports (1,2,4)), -
    _MCC> (inbound port = 4, outbound ports (1,2,3)) )
    
    Trying to be this clever by saying don't pass MOP from any of the port
    to any other port, I get :-
    
    %MCC-E-NOPARAMLIST, no parameter list was supplied in this ILV buffer
    
    Maybe, I have achieved what I was trying to do ?!!
    
    Confused, I am !!
    
    Giles.