[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
4201.0. "Can't delete multicast address" by BRAT::BUKOWSKI () Sat Dec 05 1992 19:31
Help,
I created a multicast entry for one of my DECbridge 610's and later
needed to delete it. Well, I can't. The message says I have used
an incorrect password. I double checked my password, and I even
tried a few other password required commands successfully just to
make sure I had the correct password. Since I couldn't delete the
multicast address, I had to modified the filtering to reverse the
effects. Although the modification has improperly resolved my
situation, the characteristics now show this address to have a
dispostition of filter as well as a forward map. Shouldn't this
be impossible, contradictive even?
Mike
MCC> DELETE BRIDGE .MKO.BR.MKO2G2BRG201 FORW DATA MULTI ENTRY 09-00-2B-00-00-0F,
BY PASSWORD = SECRET
Bridge DEC:.MKO.BR.MKO2G2BRG201 Forwarding Database Multicast Entry 09-00-2B-00-
00-0F
AT 5-DEC-1992 19:13:49
Invalid Password.
MCC>
MCC> SET BRIDGE .MKO.BR.MKO2G2BRG201 FORW DATA MULTI ENTRY 09-00-2B-00-00-0F FOR
WARD PORTS=(1,2,3,4), BY PASSWORD = SECRET
Bridge DEC:.MKO.BR.MKO2G2BRG201 Forwarding Database Multicast Entry 09-00-2B-00-
00-0F
AT 5-DEC-1992 19:15:08 Characteristics
Modification completed successfully.
Forward Map = ( (
inbound port = 1,
outbound ports = ( 2,
3,
4 ) ),
(
inbound port = 2,
outbound ports = ( 1,
3,
4 ) ),
(
inbound port = 3,
outbound ports = ( 1,
2,
4 ) ),
(
inbound port = 4,
outbound ports = ( 1,
2,
3 ) ) )
MCC>
MCC> SHOW BRIDGE .MKO.BR.MKO2G2BRG201 FORW DATA MULTI ENTRY 09-00-2B-00-00-0F AL
L CHAR
Bridge DEC:.MKO.BR.MKO2G2BRG201 Forwarding Database Multicast Entry 09-00-2B-00-
00-0F
AT 5-DEC-1992 19:16:06 Characteristics
Examination of attributes shows:
Disposition = Filter
Forward Map = ( (
inbound port = 1,
outbound ports = ( 2,
3,
4 ) ),
(
inbound port = 2,
outbound ports = ( 1,
3,
4 ) ),
(
inbound port = 3,
outbound ports = ( 1,
2,
4 ) ),
(
inbound port = 4,
outbound ports = ( 1,
2,
3 ) ) )
Management Created = True
Permanent = True
MCC>
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4201.1 | Problem reproduced, workaround suggested | QUIVER::WALTER | | Thu Jan 14 1993 09:11 | 64 |
| I think there are two separate problems here. One is the inability to
delete an entry even with the password, the other is the contradiction
between disposition = filter and the forward map.
Password problem
----------------
I have reproduced this problem on both a 5xx and a 6xx, each running the
latest version of development software. If a password is set, the entries
can't be deleted because of an "invalid password" error. I will log this
as a QAR. I don't know yet if the source of the problem is the bridge or
is MCC.
Workaround: Try eliminating the password before deleting the forwarding
table entry. This worked OK for me, but I didn't try it yet on older versions
of bridge firmware.
MCC> SET BRIDGE bridge_name PASSWORD "", BY PASSWORD "current_pass"
Disposition problem
-------------------
This was revealed recently as an idiosyncrasy of the 600 series bridge firmware
and of MCC software. First, here's what creates the problem:
MCC> CREATE BRIDGE bridge_name FORW DATA [STATIC/MULTI] ENTRY address
MCC> SET BRIDGE bridge_name FORW DATA [STATIC/MULTI] ENTRY address -
FORW PORTS = (1,2)
If you now show the attributes of that address, it will indicate that
disposition is filter AND forwarding ports are 1 and 2, an obvious
contradiction. By the way, I believe that in this state the disposition =
filter takes precedence and the bridge will not forward any packets with that
address.
It seems that the first part of the problem is the creation of the entry
without any attributes specified by the user. When MCC sends the message to
the bridge, it has to specify the attributes, so it uses disposition = filter
by default.
The second part of the problem is the way the 600 series bridge handles the
multi port forwarding database. Because the 600 series evolved from the 2- port
500 series bridge, it still has the disposition attribute (filter/ forward)
which applies to all 4 ports. This attribute is tested in the first table
lookup upon receiving the packet. In order to independently specify the
disposition of each port, the developers had to add another database which is
checked after a second lookup in the table. If, after the first lookup, the
disposition is seen to be "filter", the packet is discarded without checking the
second database.
So, if an entry in the table has been set to disposition = filter, and you
want to specify certain forwarding ports, you must first delete the entry
from the table, then create it again SPECIFYING THE FORWARDING ATTRIBUTES
IN THE SAME COMMAND. For example,
MCC> CREATE BRIDGE bridge_name FORW DATA [STATIC/MULTI] ENTRY -
address FORW PORTS = (1,2)
Once the entry is created this way, it can be changed using the set command.
Dave
|
| 4201.2 | MCC not sending password | QUIVER::WALTER | | Thu Jan 14 1993 13:18 | 8 |
| We've isolated the cause of the password problem. For some reason,
MCC is not including the password in the delete request packet. So the
bridge, seeing no password, is returning an "invalid password" error.
Bob Harokopus is aware of this problem and will make any necessary
changes to the Bridge AM module.
Dave
|
| 4201.3 | password bug fixed in Bridge AM | QUIVER::HAROKOPUS | | Tue Jan 19 1993 17:17 | 7 |
| The password problem was caused by the bridge AM not sending the
password to bridge. This bug has been fixed and will be in the
next release. If you need something right away let me know.
Thanks,
Bob
|
| 4201.4 | next release = ? | BRAT::BUKOWSKI | | Wed Jan 20 1993 11:04 | 5 |
| Does this mean the fix will be incorporated in the SSB release of
MCC 1.3?
Thanks,
Mike
|
| 4201.5 | Plan is to incorporate ELM fixes for 1.3 SSB | MOLAR::CHRISB::BRIENEN | Network Management Applications! | Fri Jan 22 1993 10:55 | 0
|