| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5135.1 | CLD opening soon... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Sun Jun 06 1993 21:23 | 5 |
| re: .0
Same problem seen at a site here.
I am opening a CLD on it...
thanks,
Mike
|
| 5135.2 | | ZUR01::SCHNEIDERR | | Mon Jun 07 1993 07:21 | 4 |
| Could we get some feedback of the results..... If there are fixes..........
Roland
|
| 5135.3 | now trying SNMP... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Sat Jun 19 1993 08:11 | 8 |
| re: .2
I think I spoke too soon...
I checked up with other notes about decbridge 90's and it seems that
the Bridge AM doesn't actually support them, but they should be
supported using SNMP via a DECagent 90 V1.1. I am trying to see if this
approach works before I complain too loudly :-)
Mike
|
| 5135.4 | when will it be supported? | BACHUS::DEWILDE | Patrick | Wed Sep 29 1993 11:21 | 4 |
| Are there any plans to support the DECbridge90-FL from the bridge AM?
My customer does not have SNMP...
Patrick.
|
| 5135.5 | | BERN02::FUCHS | FRED FUCHS | Fri Oct 15 1993 11:11 | 81 |
| Hi,
Recently i spent some Time on the old problem registering a DECbridge
90 FL. Here are the results.
MCC> reg bridge .telco.v.my_bridge address 08-00-2B-31-D5-E5
Bridge PTTCH:.telco.v.my_bridge
AT 13-OCT-1993 17:11:47
Partial registration success. Please retry later to complete the
registration.
Reason for Partial Registration = Communication with the target
has been interrupted
The registrations command wants to read the Bridges Characteristic's
and there, my guess, the registration fails because one can do
MCC> sho bridge .telco.v.my_bridge
Using default ALL IDENTIFIERS
Bridge PTTCH:.telco.v.my_bridge
AT 13-OCT-1993 17:16:26 Identifiers
Examination of attributes shows:
Name = PTTCH:.telco.v.my_bridge
Address = { 08-00-2B-31-D5-E5,
08-00-2B-71-D5-E5 }
or
MCC> sho bridge .telco.v.my_bridge all status
Bridge PTTCH:.telco.v.my_bridge
AT 13-OCT-1993 17:17:16 Status
Examination of attributes shows:
Bridge Function = Bridge
Management Heard Port = 1
Device State = Operating
Best Root Priority = 128
Best Root = 08-00-2B-03-F6-4C
Best Root Age = 256 Seconds
My Cost = 10
Root Port = 1
Time Since Last Hello Sent = 0 Seconds
Topology Change Flag = False
Topology Change Notification Flag = False
Topology Change Timer = 30 Seconds
Actual Hello Interval = 256 Seconds
Actual Forward Delay = 3840 Seconds
Spanning Tree Mode = LAN Bridge 100 Mode
LANBridge 100 Being Polled = 00-00-00-00-00-00
NVRAM Failed Flag = False
MCC> sho bridge .telco.v.my_bridge all ref
Bridge PTTCH:.telco.v.my_bridge
AT 13-OCT-1993 17:17:37 References
Examination of attributes shows:
Location = -- Attribute Not Available
Implementation Desc = -- Attribute Not Available
Responsible Person = -- Attribute Not Available
Phone Number = -- Attribute Not Available
MAIL Account = -- Attribute Not Available
Remarks = -- Attribute Not Available
Text File = -- Attribute Not Available
but it fails with
MCC> sho bridge .telco.v.my_bridge all char
Bridge PTTCH:.telco.v.my_bridge
AT 13-OCT-1993 17:19:10 Characteristics
Communication with the target has been interrupted
Hope it helps and may someone has a solution
Regards Fred
|
| 5135.6 | Bridge AM does not support DB90/90FL. | NPSS::WADE | Network Systems Support | Thu Mar 31 1994 16:03 | 13 |
|
It has been stated in this conference that the DECmcc Bridge AM does
not support the DECbridge90/90FL. In fact the SPD specifically states
that the Bridge AM ONLY supports the LANbridge100/150/200 and the
DECbridge 5xx/6xx.
Certain commands may work and others may not but it is not supported
and there are currently no plans to enhance the Bridge AM or the RBMS
agent on the DECbridge90/90FL to support management via the Bridge AM.
SNMP is the way to go with the DECbridge90/90FL.
|