| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 58.1 | WHY ? | BAHTAT::NAYLOR | John Naylor EIS Newcastle(UK) | Wed May 02 1990 11:48 | 9 |
| DECnet counts packets of various types at the circuit level, which it
wouldn't be difficult to write some DCL to manipulate. Obviously this
is at the node level. But anything listening to the wire is only going
to be able to count by source or destination not user.
But I agree why would anyone want to do it
John
|
| 58.2 | | KONING::KONING | NI1D @FN42eq | Wed May 02 1990 13:52 | 8 |
| If you want to count packets, we have various products that do that.
But if you want to differentiate which applications, or which users,
generates which packets, then you have a very difficult problem.
I very much doubt that Fibronics, or anyone else, has a solution to
offer either. Chances are they either misunderstood what was being
asked, or are claiming more than they can deliver.
paul
|
| 58.3 | The Fibronics Network Management Product (VAX FINEX NMS )
| BLGVS3::STRATOS | | Thu May 24 1990 15:48 | 31 |
| The Fibronics network management product is called NMS and provides the
facilities for managing FDDI rings that interconnect ISO 8802-3 (and others)
LANs. They attach computing systems on the FDDI via their FDDI Bridge product
set that uses the encapsulation mechanism for packet exchange. The resulting
FDDI ring is managed via a PC attached to one of the bridges.
Numerous FDDI rings can be managed from a remotely located PC, which in turn
communicates the NMS stations -PCs attached on the FDDI rings - and exchanges
and exchanges network management information. All PCs run DECnet-DOS (!!!) and
they use the DECnet transport mechanism and task-to-task communications.
A further improvement is offered via the VAX FINEX NMS product that runs on
a centrally located VAX - running VAX/VMS - in a DECforms environment. This
enables the network management personnel to manage diverse FDDI rings in four
network management functional areas - configuration, fault, performance and
security. Again the transport mechanism is provides by DEcnet.
I believe thay can meet this customer's requirements. They can do more via
their FDDI routers using TCP/IP and other products.
Fibronics is an extremenly aggressive company that can provide multivendor
integration (at the Data Link and/or Network Layer) today. Their presence
is mostly on DEC sites, so be very careful !!!
Regards,
Stratos
|
| 58.4 | What's the matter here? | CSC32::C_OUIMETTE | Wampeters and Foma | Fri May 25 1990 14:30 | 42 |
| Re: .3:
I'm not that familiar with the Fibronics product set, but if I
understand your entry correctly, in order to manage/report statistics
from the FDDI ring via Fibronics, you must:
1. Buy additional PC's, with (expensive) FDDI interfaces.
2. Give up FDDI phy's for usage by those PC's (.3 indicates they're on the
ring).
3. Purchase/manage DECnet/DOS on 1 or more PC's.
4. Forfeit the ability to talk between nodes on the Ethernet and the
FDDI ring (Fibronics only encapsulates to other Fibronics bridges, we
translate...).
Whereas with DECelms both bridges and Concentrators are manageable by
the installation of a single software product on an already existing
Vaxen on the Ethernet.....
Unless Fibronics' reporting abilities are vastly superior to DECelms'
(and ELMS reports just about everything one could want to manage a ring)
I don't see where they are providing the better solution; ours would
appear to be the better product (not that I'm biased in any way ;-) ).
Our products will be announced fairly shortly; "Fibronics has it now"
(if they do), would not normally be justification for what appears to
be an inferior approach, with less flexibility and more headache to
manage..... (good thing I'm not biased......)
What am I missing? Does the Fibronics mgmt interface indeed
report the gender/philosophical inclination/aura color/dietary habits
of each packet as it goes by, and we don't? All seriousness aside,
why do you believe them to have the superior solution?
Chuck O.
|