[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
3263.0. "Out of band console management" by CGOOA::BARNABE (Guy Barnabe - Digital Canada) Sun Feb 11 1996 21:03
My local telco is interested in using our stuff in a large implementation.
The network would consist of a ton of locations (3 to 500 locations),
some with 900 hubs.
They deciding between Cisco 2500 and DECbrouters. The 2500
has a console port and a auxiliarty console port. The DECbrouter
only has one port.
If they use Cisco routers, they would attach the aux console port to
the hub console, allowing them to dial into the 2500 and "attach"
to the hub console via the aux port. They normally do this
when mixing Cisco routers and Bay (Synoptics) hubs.
Now they see that the DECbrouter does not have an aux port to do this,
meaning they would need two modems per site for (total) out of band
management of hub and router.
The likely scenario is that the telco will just have one modem on the
router port and use snmp to the hub management, which means a mix
of in and out of band management. They would prefer to have complete
out of band management for both router and hub management ports.
The question(s) is:
(1) are we loosing a critical out of band management configuration option
by not having direct access to the hub port. It could be that it is very
critical to have access to the Bay hub management port... perhaps more
important then our hubs??
(2) does this give the 2500 an advantage?
Comments?
-- cheers,
Guy
T.R | Title | User | Personal Name | Date | Lines
|
---|