| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1577.1 | Try this. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Fri Oct 14 1994 16:50 | 19 |
| You click on Manage Community on the main screen. Next you would
click on Add in the community (upper half) of the screen. Add the
DECagent 90 with its IP and MAC address and name. Double click
on the square at the right hand side of the line. You will get
an Agent screen in the bottom half of the screen. Click on Add
and then add a single or double DEChub 90. You can add more DEChub
90's if you wish. Again double click on the square at the right
side of the hub line. Click on Cancel and you will now have a display
of an empty hub. To add a DECbridge 90 or 90FL, click on slot 7
or 8 then go into Add on the pull down menu and enter the information.
A DECbridge should appear on the appropriate slot. If you have
polling enabled then in a few minutes you should get a screen refresh
with all the repeaters showing. If you originally selected a single
hub but have a daisy chained hub, then that will show up on a refresh.
I haven't done this for a couple of months so I hope I renmembered
everything.
dave
|
| 1577.2 | A brief lesson in SNMP community management | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Oct 14 1994 17:37 | 19 |
| Dave's description (.1) looks pretty complete. I'll elaborate on some of the
other points.
You cannot use a single community name to manage *all* your hubs. SNMP
management is based on a unique IP address / community name pair. With the
DEChub 900's, you manage them using a unique IP address, so the community name
can be the same for many hubs. Since the DECagent 90 can manage many DEChub 90
communities (but the DECagent has only a single IP address), the community name
is what makes the pair unique.
The DECagent always has at least one community, the one that it is in. If it is
in a DEChub 90, it will discover other modules in that hub. But remote
communities must be added via HUBwatch, as Dave describes in .1, with unique
community names. By adding a DECbridge to that remote hub, the DECagent uses it
to discover the other modules in that hub.
That's the 30-second description.
...Roger...
|
| 1577.3 | I've got it with the community, one more Question | COL01::LOPEZ | Arturo Lopez drinks K�lsch at Cologne | Mon Oct 17 1994 14:06 | 16 |
| Did I understand you correctly ?
The DECagent uses a bridge 90 to autodiscover and communicate with the
modules in the DEChub.
If I do not have a Bridge on a DEChub, I have to configure the HUB
manually. How does the DECagent communicate with the DEChub90 modules
in this case (No Bridge) ?
Which protocoll does the DECagent use to communicate with the bridge ?
Which protocoll does the Brige use to communicate with the other
modules in the DEChub 90 ?
Arturo
|
| 1577.4 | There must be a hub master to manage the repeaters | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Oct 17 1994 14:29 | 30 |
| Let me be very clear about this.
In the hub in which the DECagent is installed, you DO NOT need a bridge to
manage the repeaters in that hub. The DECagent can be the hub master and manage
the repeaters. Of course, if your configuration calls for a bridge in that hub,
it is perfectly legal to install one (and manage it with the DECagent).
In a REMOTE hub, you must have a bridge installed in order to manage the
repeaters in that hub. The DECagent "speaks" the RBMS protocol (80-38) to the
bridge to manage it and the repeaters in that hub.
You cannot manage the repeaters in a remote hub without a bridge in that hub.
Manually configuring repeaters in a remote hub without a bridge in that hub will
not allow you to manage them with the DECagent. There must be a hub master
present in the hub to accomplish the management. At this time, only the
DECbridge 90/90FL is supported as the remote hub master for management with a
DECagent.
In both cases above, the hub master (the DECagent in the first hub and the
DECbridge in the remote hubs) "speaks" a protocol we call "Left Hitchcock" which
is a serial protocol transmitted on the backplane management channel. There are
other notes in this conference which explain this protocol to varying levels of
detail.
One last note. Remember that we are speaking only of the so called "dumb
repeaters" which currently consists of the DECrepeater 90C, 90T, 90T+, 90FA and
90FL. This does not include the DECrepeater 90FS and 90TS which are managed
directly using their own built-in SNMP agent.
...Roger...
|
| 1577.5 | | COL01::LOPEZ | Arturo Lopez drinks K�lsch at Cologne | Mon Oct 24 1994 05:51 | 7 |
| Roger,
thank you very much for aour explanation.
I now know the reason, why I could not see the modules in a DEChub90.
Arturo
|