[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

1690.0. "Problem with Brdge AM setting disposition to forward" by CRONIC::LEMONS (And we thank you for your support.) Tue Oct 22 1991 15:30

DECmcc EMS V2.1 SSB

I'm trying to change the disposition of a particular multicast address from
FILTER to FORWARD.  Yet, when I use a disposition of FORWARD, I get a 'Invalid
Value' error message.

What's up?

Thanks!
tl

MCC> set bridge .hlo.s.mcc.bridge.cronic for data multi ent AB-00-00-01-00-00 di
sposition=filter

BRIDGE DEC:.hlo.s.mcc.bridge.cronic FORWARDING DATABASE MULTICAST ENTRY AB-00-00
-01-00-00
AT 22-OCT-1991 13:26:56 Characteristics

Modification completed successfully.
                            Disposition = Filter
MCC> set bridge .hlo.s.mcc.bridge.cronic for data multi ent AB-00-00-01-00-00 di
sposition=forward

BRIDGE DEC:.hlo.s.mcc.bridge.cronic FORWARDING DATABASE MULTICAST ENTRY AB-00-00
-01-00-00
AT 22-OCT-1991 13:28:04 Characteristics

Problem modifying attribute.
                            Disposition = -- Invalid Value
MCC>
T.RTitleUserPersonal
Name		DateLines
1690.1Mcast Disposition = FILTER (only).CHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Tue Oct 22 1991 16:4811
For all of the bridges I've tried (LB100,LB150,LB200), Multicast Entries
only exist with disposition = FILTER. The way to "set" them to FORWARD
is to delete them from the database.

Note that this limitation is enforced by the Agent microcode, not the
Access Module.

I'm not sure whether the newer bridges allow this (I'll mail the base note
to someone in the LAN BU for comment).

						Chris
1690.2CRONIC::LEMONSAnd we thank you for your support.Tue Oct 22 1991 17:0922
Chris

Thanks for the fast reply.  If what you say is true, please have the document-
ation corrected, too.  In the 'Bridge Access Module Use' manual, on p. 4-22, I
see the following:

Select Bridge, Forwarding Database, Multicast Entry or Physical Entry,
 Entry Identifier
Operations -> Set -> Characteristics ... Disposition = Filter or Forward
.
.
.

SET BRIDGE bridge_id FORW DATA PHYS ENTRY e_addr Disposition={FILTER|FORWARD}
[, BY PASSWORD=pwd]

From this, I felt that a SET BRIDGE ... FORWARD was perfectly legal.  And
frankly, I think it should be.  Deleting an address is not intuitively equal to
SET BRIDGE ... FORWARD!

Thanks!
tl
1690.3What type of bridge are you using?QUIVER::CMIP::CHILDSEd ChildsWed Oct 23 1991 15:1017
| MCC> set bridge .hlo.s.mcc.bridge.cronic
|	for data multi ent AB-00-00-01-00-00 disposition=forward

    Is this a multiport bridge you are using?  If it's a DECbridge 6xx,
    then you cannot specify Disposition=Forward.  You must use Forward Map,
    Forward Ports, Filter Map or Filter Ports to specify which outbound
    ports are to be forwarded.  If you want every port to forward to every
    port for that address, use these commands:

    MCC> use default entity bridge <name> forwarding database -
    	 multicast entry <address>
    MCC> set forward ports (1,2,3,4)

    You are allowed to specify Dispostion=Filter, though.

    I'll make sure this is made clear in the documentation.