| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 956.1 | Why not use ISIS to propagate/export/import | STKHLM::WEBJORN | Gullik Webj�rn Network Advisory | Mon Jan 20 1997 13:17 | 5 |
| 956.2 | IS-IS on just 1 routeabout ? | COPCLU::JENS | | Mon Jan 20 1997 14:24 | 10 |
| 956.3 | It should shouldn't it? | STKHLM::WEBJORN | Gullik Webj�rn Network Advisory | Tue Jan 21 1997 10:19 | 11 |
| 956.4 | propagation via RIP | COPCLU::JENS | | Fri Jan 24 1997 12:22 | 17 |
| Hi again !
The routeabout does not send IP information with IS-IS, nor
does it listen to IS-IS ip-updates. So the only way to get it working
was to have 1 wanrouter export/import rip into IS-IS. The routeabout
sends RIP by default. In the routeabout I made a static route that
points to a wanrouter as default gateway and so it came to work.
Also I tried to make 1 routeabout as an OSPF-boundary ruter but as
a boundary-router there is no possibility to import/export IS-IS into
OSPF only RIP and EGP and static routes.
Best regards
Jens
|
| 956.5 | Ok, so it's a restriction in the RA then... | STKHLM::WEBJORN | Gullik Webj�rn Network Advisory | Fri Jan 24 1997 15:17 | 9 |
|
Hmm,,
I did not test running multiple IP routing protaos at the same time,
but I definitely managed to set it up to route both OSI and IP with
I+ISIS
Gullik
|
| 956.6 | Int-ISIS does work on RouteAbout | MARVIN::TURNER | Neil Turner IPEG REO, 830-4140 | Thu Jan 30 1997 16:18 | 8 |
| The RouteAbout DEFINITELY supports Integrated-IS-IS and WILL import RIP
routes into I-ISIS. You need to issue the ENABLE INTEGRATED-ISIS
command at the OSI Config> prompt.
However the RouteAbout 90 cannot run OSPF and I-ISIS at the same timer due
to memory/CPU restrictions.
Neil
|