| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 865.1 | | MARVIN::CLEVELAND | | Fri Apr 18 1997 07:46 | 5 |
| Today there is no routing on the VNswitch, but an upcoming release will
add IP routing. In that version, yes, you will be able to route IP via
the VNBUS.
|
| 865.2 | What about MP? | ALBANY::BARTLEY | | Fri Apr 18 1997 13:56 | 7 |
| Will the future release add MultiProtocol Routing? I want to replace a
DECswitch 900EF that is running MP. Still alot of LAT, etc.., running
around out there.
Thanks,
Dave
|
| 865.3 | IP routing only | CSC32::bngpc.cxo.dec.com::goodwin | Brad Goodwn - NSIS | Fri Apr 18 1997 14:07 | 1 |
| Nope, it is IP routing only. No MP.
|
| 865.4 | Can I bridge everything else? | ALBANY::BARTLEY | | Fri Apr 18 1997 14:43 | 5 |
| When you say IP routing only, will it bridge all other protocols?
Thanks,
Dave
|
| 865.5 | | CSC32::bngpc.cxo.dec.com::goodwin | Brad Goodwn - NSIS | Fri Apr 18 1997 14:56 | 2 |
| yes, it will route IP, from what I understand using RIP or OSFP, and
bridge everything else.
|
| 865.6 | | MARVIN::CLEVELAND | | Mon Apr 21 1997 03:59 | 5 |
| The next release will route IP, just like a WGE would (same routing
protocols, etc). Additional protocols are being considered for future
releases (ie, make your case to product management).
Tim
|
| 865.7 | Just RIP and OSPF Routing Protocols | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Mon Apr 21 1997 04:17 | 4 |
| VNS V2 will only support RIP and OSPF as routing protocols. So it won't support
integrated ISIS and Multicast routing.
Tony
|
| 865.8 | Why no MP? | ALBANY::BARTLEY | | Mon Apr 21 1997 12:38 | 12 |
| Why no Multiprotocol version? Are the other protocols dying a slow
death? Is Digital going to stop selling DECnet licenses on Alphas and
Vaxes.
I am anticipating some customer questions.
Is it for perfomance in the VNswitches? Will the MP still be available
for the DECswitches?
Thanks,
Dave
|
| 865.9 | business decision | FORBIN::WILKINSON | | Mon Apr 21 1997 14:32 | 6 |
| The decision as to which protocols are routed on the VNswitch is
purely a business decision. Technically, the VNswitch can suuport
routing all of the popular protocols -- its just a matter of software.
Forward your requests and business case to product management.
Hugh
|
| 865.10 | | ALBANY::BARTLEY | | Mon Apr 21 1997 15:40 | 5 |
| I think I will. Who is Product Management for Routing Code?
Thanks,
Dave
|
| 865.11 | How is the VNbus used? | ALBANY::BARTLEY | | Mon Apr 21 1997 16:28 | 17 |
| I would like to clarify how the VNbus will work using it with
VNswitches running IP code.
1. Will the VNbus be treated as a subnet wire? If I want to route
across the VNbus, do I have to assign it a subnet?
or
2. Will the VNbus join VNswitches together to make one big VNswitch
router like the way IMBs make multiple repeater/PORTswitch modules
into a big repeater?
Thanks,
Dave
|
| 865.12 | | MARVIN::CLEVELAND | | Tue Apr 22 1997 05:00 | 6 |
| Sorry to cause any confusion...
It is RIP & OSPF only; no BGP/MOSPF/DVMRP...or Int-IS/IS of course,
since it supports no OSI at all.
Tim
|
| 865.13 | | IROCZ::GUNNER | | Tue Apr 22 1997 08:45 | 19 |
| re .11:
1. Will the VNbus be treated as a subnet wire? If I want to route
across the VNbus, do I have to assign it a subnet?
or
2. Will the VNbus join VNswitches together to make one big VNswitch
router like the way IMBs make multiple repeater/PORTswitch modules
into a big repeater?
Each VNswitch module acts as a separate router. To communicate across
the VNbus, you configure one or more VSDs (VLANs) to include the VNbus
and then you configure a routing virtual interface over each VSD. So,
the VNbus will be a member of one or more VSDs, each of which may have
a routing virtual interface attached and each routing virutal interface
will have its own subnet address(es).
Chris
|