| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 12.1 | Not yet, but when the DENMA ships | NOHOST::LEVIN | Bryan, LENaC Engineering, MLO3-3/U39 | Thu Dec 12 1991 11:24 | 9 |
| Jeff,
It is being implemented as we speak. It will be there when the DENMA
releases, since the DENMA speaks to the DEWGB via RBMS, and -not-
MOP/CC.
Stay tuned ...
.bl
|
| 12.2 | Use MOP to spoon-feed the bridge | NOHOST::LEVIN | Bryan, LENaC Engineering, MLO3-3/U39 | Thu Dec 12 1991 11:26 | 7 |
| Oh, BTW, the DEWGB is upgradable (ie, the FLASH image) via MOP
down-line load. So, the new 'wgb_flash.exe' (or whatever it's called)
will be provided to allow upgrades. That is, internally it will be
available. I'm not sure how we'll upgrade the WGB's for customers.
(Jack or Bill ?)
.bl
|
| 12.3 | Timescales? | SHIPS::SMITH_J | Jeff Smith | Fri Dec 13 1991 07:36 | 5 |
| Thanks for the prompt responses.
Can you give me some idea of how long it will be before my customer can
use it? The like the hubs a lot, but are getting pushed by other
groups who demand managment from the likes of a DECmcc station.
|
| 12.4 | if SNMP management is the issue...
| ASDS::BARLOW | i THINK i can, i THINK i can... | Mon Dec 16 1991 16:00 | 14 |
|
You may want to read the earlier note on SNMP managability,
if your customers are demanding management. They will quite
soon have the choice of DOS or ULTRIX-based SNMP management
through either David Systems or MSU. Following soon after,
management through DECMCC should also be available. Personally,
I've used MSU/ELMS to query the WGB on my desk. (I wrote the
ELMS front-end in MSU and I'm working with Bryan Levin on
HUB/MSU integration.)
Rachael Barlow
|
| 12.5 | Schedule for graphical hub management | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Mon Dec 16 1991 17:01 | 6 |
| Graphical hub management will FCS some time in Q4, FY92 (by 1 July).
Beyond that, my crystal ball is fuzzy. I should have seed units in
early February. Let me know if you are interested.
P.S. Graphical management will be thru MSU, MCC, and a new DOS based
system. Your customer can choose the style he likes best.
|
| 12.6 | HUBwatch for X-windows (MCC and MSU) | NOHOST::LEVIN | Bryan, LENaC Engineering, MLO3-3/U39 | Mon Dec 16 1991 18:40 | 21 |
| Regarding the graphical styles:
I see only two that we'll offer. One for the DOS systems (MS windows
3.0) that is being engineered via David Systems, CA. The other one is
what Rachael and I are working on, and that *should* be identical
between MSU and MCC - as far as the look and feel. The idea is that
once you've 'launced' our application ("HUBwatch") from either the MSU
or MCC environment, most daily tasks will be 'point-and-click', and
done from within HUBwatch. At least, initially, that's what's being
planned.
At this point, the graphics are identical on the VMS and Ultrix side.
If all goes as planned, it will stay that way. BTW, we're using Motif
as our toolkit for our GUI. I know the current version of MSU is XUI
(ie, what most folks think of as DECwindows). I'm not sure what the
1.2 version of MCC will be using as their toolkit for Xwindows, but I
hope in the near future, it will be Motif. Note, that DEC is
converting over to Motif, so you better like the look/feel of Motif,
'cause it's here to stay! ;-)
.bl
|
| 12.7 | DECelms support before HUBwatch? | SHIPS::SMITH_J | Jeff Smith | Tue Dec 17 1991 07:41 | 10 |
| Can I just clarify things. My customer already has DECelms and wants
to check on the DECbridge 90 from it. Is he going to have to wait for
the HUBwatch pieces, or is the PROM upgrade going to be released
earlier. I would like the latter, since we have management of all the
other bridges from DECelms, and will soon have it from a DECmcc
station. July 1 is a long time to be unmanaged.
Regards,
Jeff
|
| 12.9 | | QUIVER::CHILDS | Ed Childs | Tue Dec 17 1991 10:08 | 26 |
|
| Can I just clarify things. My customer already has DECelms and wants
| to check on the DECbridge 90 from it.
There is no longer any development going on for DECelms. No support
for the DECbridge 90 will be done.
| I would like the latter, since we have management of all the
| other bridges from DECelms, and will soon have it from a DECmcc
| station.
DECelms does not manage all of Digital's LAN and DEC bridge series.
DECelms does not support the DECbridge 600 series.
DECmcc Extended LAN Manager V1.0 has been shipping since the summer.
It supports LAN Bridge 100, LAN Bridge 150, LAN Bridge 200, DECbridge
500 series, DECbridge 600 series, and the DEFCN DECconcentrator 500.
It currently does not support the DECbridge 90.
DECmcc ELM V1.2 will be entering field test soon. It will include MCC
Access Modules for Bridge, Concentrator and FDDI station, as well as
Function Modules for Bridge Spanning Tree Map and FDDI Ring Map.
DECmcc ELM will run on both VAX/VMS and RISC/ULTRIX platforms. Alas,
there is no support for the DECbridge 90 there either, since the
RBMS management firmware for the bridge is not ready yet.
|
| 12.10 | Clarification | ASDS::BARLOW | i THINK i can, i THINK i can... | Tue Dec 17 1991 10:36 | 41 |
|
> DECelms does not support the DECbridge 600 series.
true, but both MSU and DECMCC do support these bridges.
Also, as a clarification, all the devices which are
currently supported by DECMCC are also supported by MSU. The
supported list for MSU follows:
LB 100
LTM 100
LB 150
LTM 150
LB 200
DECbridge 500 series
DECbridge 600 series
DECconcentrator 500
I currently have on my desk a WGB which is in the
testing and development phase. Just for my own
curiousity, I used my MSU/ELMS front end to query
the WGB. It did query it but it didn't return as
many variables for commands like "show char", as I
expected. Barry Colella, who wrote the elms api which
actually communicates with the bridge, coded in some
support for the WGB. So, although customers can't get
this bridge yet, I can say that as it stands now, I
can communicate in a minimal way with the bridge using
the currently-released MSU/ELMS. I would guess that
MCC may have this same capability but since I work on
MSU, I can't say for sure.
So, I think you need to use the release date of the WGB
with RBMS support as the critical path to meeting your
customer's needs. Also, the degree of support which will
exist within MSU/ELMS and probably also within MCC/ELMS
is still tbd, (to be determined). In addition, it seems
to be critical that your customer have ELMS from either
DECMSU or DECMCC. Standard VMS ELMS doesn't support as
much as we do.
Rachael Barlow
|
| 12.11 | | QUIVER::CHILDS | Ed Childs | Wed Dec 18 1991 11:17 | 25 |
|
| Also, as a clarification, all the devices which are
| currently supported by DECMCC are also supported by MSU.
Does this include FDDI stations?
| I can say that as it stands now, I
| can communicate in a minimal way with the bridge using
| the currently-released MSU/ELMS. I would guess that
| MCC may have this same capability but since I work on
| MSU, I can't say for sure.
I work on MCC. There's isn't any support for the WGB yet, and I
haven't heard anything about when this support will be added. I work
on the Bridge AM and haven't heard when/if DECbridge 90 support will be
added.
| Standard VMS ELMS doesn't support as
| much as we do.
What is "Standard VMS ELMS" ???
Does MSU generate bridge spanning tree maps? Does MSU generate FDDI
ring maps?
|
| 12.12 | | ASDS::BARLOW | i THINK i can, i THINK i can... | Thu Dec 19 1991 09:48 | 22 |
|
re .11
> Does this include FDDI stations?
No, MSU does not currently support FDDI stations. Just as MCC has
FDDI support for it's next release, so does MSU.
> Does MSU generate bridge spanning tree maps? Does MSU generate FDDI
ring maps?
No, not in the currently-released product.
>What is "Standard VMS ELMS" ???
That is the ELMS software which runs on VMS but is not tied in
with any network management platform.
I hope this clarifies the apparent confusion.
Rachael Barlow
|