| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 60.1 | reply | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Fri Sep 25 1992 16:22 | 1 |
| reply was sent directly to mr Banks and I do not have a copy.
|
| 60.2 | DECbrouter 90 'disco' functionality | WARNUT::PC0533::Tim_Banks | Wot Ho! | Tue Oct 27 1992 08:31 | 44 |
| Here are the answers I got to the previous questions.
They beg some more questions, particularly the comment about 'if IGS does
it now, so will the DECbrouter'. Does this mean other cisco features will
be implemented?
Tim
-----------------------------------------------------------------------------
1. will it support NCL?
NO. You have to TELNET or MOP or LAT to it to set DECnet parameters.
> 2. will the bridging work with a NIS on the other end?
Yes, it should, but only if the NIS people implement the PPP extension
for Bridging and accept Cisco's bridge options. My understanding is
that NIS does NOT do this today, but will in a future release.
> 3. will it support Manually configured reachable addressing?
I don't know. We didin't explicitly ask for it in the requiresments
document, but if the Cisco IGS does it now, it will also be in Brut.
> 4. will it support manually configured adjacencies?
I don't know. We didin't explicitly ask for it in the requiresments
document, but if the Cisco IGS does it now, it will also be in Brut.
> 5. will it support Integrated IS-IS (i.e. real Phase V as per
> NIS)?
Yes, we asked for this, and won't ship it until it works.
> 6. will it do all this in V1.0?
It is likely that:
- It will never do NCL
- The DISCO side of bridging will be in our V1.0, you will have
to ask the NIS group when they will have PPP.
- Integrated IS-IS will be in 1.0
although, what you call 1.0 is actually "9.2".
|
| 60.3 | PPP Bridging on NIS in V2.0 | MARVIN::COBB | Graham R. Cobb (DECNIS development), REO2-G/G9, 830-3917 | Tue Nov 17 1992 15:40 | 17 |
| I know this note is old but it is a while since I looked in here...
> > 2. will the bridging work with a NIS on the other end?
>
> Yes, it should, but only if the NIS people implement the PPP extension
> for Bridging and accept Cisco's bridge options. My understanding is
> that NIS does NOT do this today, but will in a future release.
We are shipping PPP Bridging in the DECNIS inV2.0 (before Christmas this
year). I *think* that cisco bridging over PPP requires at least V9.1 and
that is currently unavailable (rumour has it that they are having stability
problems with 9.1 and have delayed releasing it). We are trying to get 9.1
here for interoperation testing. However, our PPP testing to date leads us
to believe that it will work as long as Cisco implement the spec (and I
expect they will): it currently works with other vendors.
Graham
|
| 60.4 | HUBwatch and DISCO ? | ANNECY::POULAIN | | Wed Jan 20 1993 11:46 | 7 |
| What is going to be the support from HUBwatch ? If I understand well, since the
s/w will be Cisco's 9.x, it'll have SNMP in it right away. Will HUBwatch be able
to manage it directly (no need for DECagent ?) ? What kind of graphics ? If
HUBwatch is able to manage it directly, what would prevent it to manage ANY Cisco
router which is out there ?
Francois
|
| 60.5 | DECagent 90 not needed to manage DECbrouter 90
DEChubs, DECbridge 90s, or DECserver 90Ls or L+s by a router. | MEMIT::FORREST | | Wed Jan 20 1993 15:15 | 11 |
|
My understanding is that the DECbrouter 90 will have GETS, but not
SETS - same as cisco. The DECagent 90 isn't needed to manage the
DECbrouter 90 - HUBwatch will talk to it directly. You will need
to use TELNET to change parameters in the module.
I would guess that to the extent that other cisco devices have
identical MIBs, they would be manageable with HUBwatch. We have
no plans though to manage cisco's entire product line with HUBwatch.
jack
|