| In talking with some engineering folk...they wondered about "why do you
use the DECbridge anyway etc.."
Just FYI...
Traditionally I'd approached selling the DEChub 90 against the
competition by saying:
- Management can be easily ADDED if you want it, making it a lower
cost of entry than the competition
- Adding a DECbridge/Agent combination, the DECbridge is 'not just
another pretty do-nothing module' but it's actually helping to
protect your LAN by providing isolation (on nasty media faults) as
well as traffic filtering, so it's a management ENHANCEMENT that
buys you LAN integrity and bandwidth
- Our wonderful DECagent does 16-fold duty by allowing you to manage
MULTIPLE hubs with DECbridges in the same LAN....so the cost of
overall management with DEChubs becomes REALLY ATTRACTIVE when
considering the competition....THEY need a one-to-one management
module ration where WE give you all this feature/functionality....
So....sorry, but that's why the ugly, silly little old left-hitchcock
MOP and RBMS only DECbridge 90 gets/got sold out there. Because in the
past it was needed to manage the hub.
The new enhancements with the TS/FS are really great and help us reduce
cost....but there are those older configs to deal with....
u c?
thanks,
j
|
| I'd like to clarify something about management of the DECrepeater
90TS/FS. Granted: Jon is correct that when the repeater is in a
remote hub managed by a DECbridge, double clicking on it in a Hubwatch
window will not bring up the repeater summary screen. This is because
the DECagent doesn't know the repeater's IP address, and doesn't even
know that the module is a repeater. It only knows its mac address,
because that is all the bridge forwards to the Agent.
The repeater CAN be managed, however. You must do it by adding the
repeater to the Hubwatch agents table, then selecting it from the
Manage Table menu. This is certainly less convenient than just
double-clicking on the module in the hub screen, but I don't think it
is so inconvenient that you would buy another Agent and put it in the
remote hub just to give you the point and click behavior. (My opinion;
others may disagree.)
I think this begs the question: Can Hubwatch match a mac address of an
unknown module with an entry in the agents table to determine how to
manage the module? If this could be done, it would solve the above
problem, the only extra work being adding the repeater to the agents
table.
Dave
|