| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1727.1 | | NETCAD::SLAWRENCE | | Mon Nov 28 1994 16:20 | 27 |
|
It is correct that if you factory reset the hub, then any configuration
information including the read/write community must be re-entered.
After changing the community, you must do a 'normal' reset in order to
propogate the community to the slots, but your example is incorrect:
1) Factory reset hub
Hub community is now 'public'
Slots are 'public-X'
2) Change hub community to 'foobar'
Hub community is now 'foobar'
Slots are 'public-X'
3) Reset hub manager
Hub community is now 'foobar'
Slots are 'foobar-X'
Note that the 'foobar-X' community for the slot applies _only_ to SNMP
operations made through the IP address of the hub; if the module has
its own IP address, then it's community must be set through it's
console (as the IP address was), and will default to 'public'.
|
| 1727.2 | What happens when I do "2 <CR>"? | CGOS01::DMARLOWE | Have you been HUBbed lately? | Mon Nov 28 1994 17:19 | 17 |
|
> 2) Change hub community to 'foobar'
>
> Hub community is now 'foobar'
> Slots are 'public-X'
>
> 3) Reset hub manager
>
> Hub community is now 'foobar'
> Slots are 'foobar-X'
When you reset the hub manager, you will do a (2) Reset with current
settings. What effect will this have on a hub with FDDI, 6 Ethernets
and 400-500 PC's? Can this be done during the day and not affect
the users?
dave
|
| 1727.3 | Nit | KEIKI::WHITE | MIN(2�,FWIW) | Mon Nov 28 1994 18:01 | 8 |
|
Re .1
After changing the community from public to hub1 but before I do a
reset of the hub itself, doing a community manage current shows
hub1 for all the slots, not public-x.
Bill
|
| 1727.4 | | NETCAD::SLAWRENCE | | Wed Nov 30 1994 13:22 | 5 |
|
That's exactly the problem - HUBwatch is using hub1, but the modules
are still using public; that's why you need the reset - to propogate
the correct (hub1) community.
|
| 1727.5 | And if I do that what happens? | CGOS01::DMARLOWE | Have you been HUBbed lately? | Wed Nov 30 1994 13:49 | 6 |
| Scott,
What is the affect of doing a "Reset with Current Settings" on a
hub in full production, ie. 1 FDDI/6 Ethernets"?
dave
|
| 1727.6 | | NETCAD::SLAWRENCE | | Wed Nov 30 1994 14:19 | 18 |
|
A "Reset with Current Settings" on a hub with active backplane channels
will cause a brief interruption on those channels as the hub
configures the backplane.
For most connections (repeater - repeater or concentrator -
concentrator, for example ) it is short enough that few if any end-user
applications (even LAT :-) will notice. For bridge backplane
connections, the bridge sees the port state change and goes back into
the listen/learn cycle (it can't tell that it was reconnected to the
same LAN), so the break is at least that long (45 seconds, if I
remember correctly).
I don't have any measurements of how long the interruption is, and it
may vary depending on the configuration; probably a nice project in
there for someone; any volunteers :-) ?
|
| 1727.7 | Hit <CR> and run like hell. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Wed Nov 30 1994 14:34 | 14 |
| I'll suggest to my customer. They have 2 switches in the hub, one
for PE to individual servers and the second one supplies switched
Ethernet to the floors via a 900FP. They are supporting 400-500
PC clients.
I'll ask him if he wants to try a reset during the day and watch
his reaction. But maybe he would schedule it over a lunch. I don't
want to be there when he does it as the support people already cringe
everytime I come around. Personally I think I've been given a bum
rap. 8^)
Let you know what happens.
dave
|