| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2403.1 | Chipcom is working on it | BIKINI::KRAUSE | European NewProductEngineer for MCC | Wed Mar 25 1992 08:04 | 10 |
| > Would a specific AM be more useful?
> I am thinking to start developement in that direction.
As far as I know Chipcom is already developing an AM for their hub.
Maybe one of the SVP people can confirm this.
Chipcom also thinks about restructuring their MIB to make it easier to
use. I don't know any dates, though.
*Robert
|
| 2403.2 | A vote for SNMP vs native Chipcom | GLDOA::MORRISON | Dave | Wed Apr 01 1992 00:26 | 3 |
| One thing is certain. Chipcom's own hub management product is fraught
with problems. My customer prefers what he has seen of managing Chipcom
with SNMP on MCC vs the Chipcom product.
|
| 2403.3 | | TOOK::R_SPENCE | Nets don't fail me now... | Mon Apr 06 1992 14:11 | 3 |
| Gee, that's good news :-)
s/rob
|
| 2403.4 | NCS versus SNMP AM ? | BRSSWS::FOLENS | | Tue Apr 07 1992 10:31 | 20 |
| re .2
>One thing is certain. Chipcom's own hub management product is fraught
>with problems. My customer prefers what he has seen of managing Chipcom
>with SNMP on MCC vs the Chipcom product.
Do you mean that you're customer doesn't like the Chipcom's NCS
management station?
If we could implement in DECmcc the functions that you can do with the
NCS station concerning the ONline concentrator then we would have a
great product. But for the moment we can only dream of this.
My collegeau, the orginator of this discussion is busy to adapt the
MIB of Chipcom to get some more functionality in it. And via this note
entry we wanted to know if there's some interest for it. I'm sure that
a lot of these concentrator boxes are installed at our customer sites
and those customers want to manage these boxes in a simple way.
So if there's enough demand for it, we can put some effort to get it
work in the right way and then we could make it available to our
customers $$$$$.
-Geert-
|
| 2403.5 | New Chipcom agent will soon be available. | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Thu Apr 09 1992 00:40 | 9 |
| My customer has taken a keen interest in Chipcom products, as of late.
He is not pleased with the agent provided. He is working on getting a
new agent (soon to be available from Chipcom).
Any added value we can provide will always be viewed favorably by
customers. Have you any information on new management module agent
developments from Chipcom?
-Dan
|
| 2403.6 | In France too... | BALZAC::COULON | Even if it works, ask why | Thu Apr 09 1992 10:10 | 23 |
|
If we do want to manage "complex" entities from MCC, then we have to provide a
very friendly user interface. You just cannot manage things using "attributes"
like "THiSaTtRIBuTEiSnOTtHaTeASYtOrEaD"... Operators (customers) need (want)
something like the NCS product, something like the "Look into" option of the
IMPM but more powerful, with less clicks and more "sexy" (What You See is What
You Have).
To come back to Chipcom, we really need a solution here in France for some
fairly large customers (Peugeot...).
1. Can we have a CLEAR status of what's going on with Chipcom, who is doing
(or not doing) WHAT, WHEN and WHERE (anything in Europe?)? Is Chipcom really
working on a new module? What about the DEC HUB?
2. Is it possible to "translate" MIB attributes before displaying them? For
example, "chipGenFepromvers" could be displayed as "PROM Version". This would
make the SNMP AM "usable" to manage Chipcom (SNMP) entities. Any way to do
this?
Regards,
Serge
|
| 2403.7 | New names for SNMP Attributes... | CHRISB::BRIENEN | DECmcc LAN and SNMP Stuff... | Thu Apr 09 1992 10:36 | 21 |
| > 2. Is it possible to "translate" MIB attributes before displaying them? For
> example, "chipGenFepromvers" could be displayed as "PROM Version". This would
> make the SNMP AM "usable" to manage Chipcom (SNMP) entities. Any way to do
> this?
DECmcc takes the names contained in the Vendor's MIB(s) and uses these
as presentation names. The example you give in the base note is
EXCELLENT ("THiSaTtRIBuTEiSnOTtHaTeASYtOrEaD")...
(Almost) nothing prevents you from editing the MIB (or MS created from
the MIB) to change the object/attribute names.
The caveats include:
1. Documentation/maintenance headaches (what if vendor releases a new
MIB, what if "something goes wrong", etc)
2. MCC Syntax rules (e.g. uniqueness of names, etc)
Hope this helps,
Chris
|
| 2403.8 | See not 1721 for more on chipcom | DANZO::CARR | | Mon Apr 13 1992 16:36 | 2 |
| Note 1721 also addresses some of the concerns regarding managing chipcom online
hubs...
|