| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3369.1 | Why can't we set up forwarding for 80-38 on DECbridge 610? | OSLACT::BJORN | Woops, now I have to learn changing diper's | Mon Jul 20 1992 07:03 | 25 |
| The problem described in .0 is as follows;
When creating an entry for the Bridge management protocol in the protocol
database on a DECbridge 610, an error message is returned. When doing
MCC> USE BRIDGE .HSK.HDA.BOX.DB1 PROTOCOL DATABASE
MCC> CREATE ETHERNET ENTRY 80-38 DISPOSITION=FORWARD
the error message "management protocol error" is returned.
The customer wants to set up default filtering for Ethernet, SAP and SNAP,
and then allow certain protocols to be forwarded. It seems fair to not touch
the 80-38 when setting up default forwarding but filter on some. But in this case
they want to do it the other way.
The same message is returned when trying to CREATE SAP ENTRY AA.
Can anyone from the ELM group comment on this? The customer wants to implement
this now, but they will get a problem with remote management of their bridges.
They could use SNMP, but they prefer the ELM way of doing it, as they have been
using RBMS and DECelms before.
Any comments?
Bj�rn Olav Haugom
|
| 3369.2 | | SLINK::CHILDS | Practice passive aggression. | Mon Jul 20 1992 17:20 | 16 |
| --> Please provide a way to do this with DECmcc-ELM !
There is no way to accomplish what you want to do with DECmcc ELM (or
any network management software).
I tried to duplicate your problem with a DECbridge 620 and I did get
the same error message. The error is being returned by the agent
software that is running on the bridge, it is not an error generated by
DECmcc or the network management software.
The agent is returning error code 133 which is "Invalid parameter
value." I can ask some of the bridge firmware/hardware developers for
more details about why 80-38 and AA are invalid values.
This is not a DECmcc issue, it's a bridge issue. I will post the
information I get from the DECbridge firmware engineers.
|
| 3369.3 | I'm the one who originally had this problem. | OSLACT::BJORN | Woops, now I have to learn changing diper's | Tue Jul 21 1992 05:32 | 6 |
| I hope the DECbridge firmware engineers come up with something real fast. If not,
we have a big problem in defending our guidelines given in the Bridge Access
Module User manual, where we are informed that we really can filter all protocols
and forward a few.
Bj�rn Olav Haugom
|
| 3369.4 | How can we set up default filtering and forward a few? | OSLACT::BJORN | Woops, now I have to learn changing diper's | Thu Aug 27 1992 09:06 | 8 |
| Any response from the DECbridge firmware engineers, yet?
The customer is now suffering from not being able to do remote management to his
DECbridges.
Who must I talk to to get a patch or a new prom or something?
Bj�rn Olav
|
| 3369.5 | | SLINK::CHILDS | The Fringe | Wed Sep 02 1992 15:39 | 10 |
| I posted this note in the bridge developers file and no response, so I
contacted one of the engineers in person and here's what I got.
Not being able to forward 80-38 protocol. This is a known bug and will
be fixed in the next release (field test in October, customer ship in
December).
AA protocol is a special type. It will automatically forward even if
all SAPs are set to filter, so you don't need to issue a command for
it.
|
| 3369.6 | how does 80-38 get set to FILTER? | SASE::RAUHALA | | Thu Oct 01 1992 16:06 | 8 |
| If I understand this problem correctly, the "other" protocol types
is being set to FILTER by the user, which causes 80-38 to be filtered,
so they then SET 80-38 to FORWARD which fails, correct?
Since 80-38 is normally forwarded, I can't see any other reason for
wanting to set it to FORWARD.
thanks.
|
| 3369.7 | you got it right | QUIVER::HAROKOPUS | | Thu Oct 01 1992 16:18 | 16 |
| re .6
Yes this is correct. The user wants to filter most ethernet protocol
types and forward just a few. The easiest way to do this is to
set the default ethernet protocol filtering to false and then
set the disposition to forward on the individual ethernet protocols
to be forwarded.
The problem is that the firmware sets bridge managment 80-30 to
filter when this is done. It should never allow this to happen.
The bridge firmware engineers know about this problem (they have
received a customer CLD) and they are working on a fix.
Regards,
Bob
|