| Title: | DEC Network Integration Server (DECNIS) |
| Notice: | Please read note 1 to use this conference effectively |
| Moderator: | MARVIN::WELCH |
| Created: | Wed Sep 18 1991 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3660 |
| Total number of notes: | 15082 |
Hello!
For test purposes i wanted to configure a DECnis600 Version V3.1-9 with an
MPC-III card.
At Level 1 the routing protocol should be "Routing Vector" and at
Level 2 "LINK State".
The NCL script told me, that i did right.
.
.
set routing manual L1 algorithm routing vector
set routing manual L2 algorithm link state
set routing Integrated ISIS protocols { ISO8473 }
.
.
After a reload the router told me
Manual L1 Algorithm = Link State
Manual L2 Algorithm = Link State
So i tried do manually set the L1 Algorithm. This worked as long as i included a
ROUTEABOUT Access EW/MP on the same net.
This routeabout is also configured as L1( routing vector) and L2 (Linkstate)
and has the same behaviour . Both, L1 and L2 are Linkstate after restart.
*
t 6
config>p osi
OSI_config>list algo
OSI config>list algo
Level 1 Algorithm = DISTANCE_VECTOR
Level 2 Algorithm = LINK_STATE
==Restart
t 5
+ p osi
OSI>dnav
DNAV Level 1 Routing Algorithm: LINK_STATE
DNAV Level 2 Routing Algorithm: LINK_STATE
At the RouteAbout i'm not able to manually set the right algorithm.
But the interresting fact is, that the Decnis had a "Software Crash" at the
moment i restarted the Routeabout.
Is there something i forgot in my config ??
Could there be a bug using MPC-III cards and V3.1-9 (V4.0 is the next step i
will try) ??
Another DECNIS with MPC-I and V3.1-9 works correct with the same config.
Any help will be highly appreciated.
Thanks,
Wolfgang
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3580.1 | MARVIN::PATEL | Wed Mar 26 1997 05:05 | 54 | ||
The version of MPC you have in the DECNIS does not affect the way the
routing protocols operate ( apart of course from being faster on an MPC
III).
>The NCL script told me, that i did right.
>.
>.
>set routing manual L1 algorithm routing vector
>set routing manual L2 algorithm link state
>set routing Integrated ISIS protocols { ISO8473 }
>.
>.
>After a reload the router told me
>
> Manual L1 Algorithm = Link State
> Manual L2 Algorithm = Link State
This seems to imply that you are loading a different script into the DECNIS
from the one where you set the algorithm to 'routing vector'. Is the script
being loaded from the network or flash ? If it is being loaded from flash
make sure the correct flash area has been chosen.
>So i tried do manually set the L1 Algorithm. This worked as long as i included a
>ROUTEABOUT Access EW/MP on the same net.
Changing routing algorithms on the fly will not work and will result in
unexpected behaviour. The fact that the DECNIS allows you change the
algorithm on the fly is a bug.
>This routeabout is also configured as L1( routing vector) and L2 (Linkstate)
>and has the same behaviour . Both, L1 and L2 are Linkstate after restart.
This does not make sense at all. The presence/absence of other routers does
not affect the configuration of the DECNIS. The DECNIS will configure
itself according to what is in the cmip script.
>But the interresting fact is, that the Decnis had a "Software Crash" at the
>moment i restarted the Routeabout.
Can you supply a crash dump so that we can analyse it ?
>Is there something i forgot in my config ??
>Could there be a bug using MPC-III cards and V3.1-9 (V4.0 is the next step i
>will try) ??
>Another DECNIS with MPC-I and V3.1-9 works correct with the same config.
The most likely explanation is that the DECNIS is not loading the script you
think it should. Going to V4.0 will not make a difference and as I said
before the version of the MPC card does not affect the way the routing
protocols operate.
Jitu
| |||||
| 3580.2 | Loaded the right image did it! | UTOPIE::BERG_W | Wed Mar 26 1997 09:28 | 8 | |
Sorry,sorry,sorry........
As you aspected, the router was loaded from another host.
Thank you very much for your answer.
Wolfgang
| |||||