[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hierarchical, multicast routing etc
On Wed, 30 Sep 1998, Padmaparna Haldar wrote:
> On Wed, 30 Sep 1998, Polly Huang wrote:
>
> > It seems to me that the following error is due to the change in
> > link/node indexing for hierarchical routings. Am I right, Padma?
>
> Hierarchical rotuing uses the same link indexing (using node ids) as does
> flat rtg.
I shouldn't be using hierarchical routing; that only kicks in when you
have more than one routing level, yes? Not with:
$ns set-address-format hierarchical 1 9
or similar. In any case, since they use the same link indexing, it's
a moot point.
> looks like either the link_ array was not created completely or
> CtrMcast is trying to use a non-existing link?
CtrMcast encountered a simplex link, and apparently didn't know what
to do with it. Is CtrMcast assuming that links are duplex even when
they're not?
thanks,
L.
and the IETF UDLR group is addressing similar problems in RL.
> --Padma.
>
> > -Polly
> >
> > > As for simplex errors with CtrMcast:
> > >
> > > ns: _o3116 join-group _o5342 0x8000: can't read "link_(6:5)": no such
> > > element in array
> > > while executing
> > > "return $link_($from:$to)"
> > > (procedure "_o4" line 6)
> > > (Simulator RPF-link line 6)
> > > invoked from within
> > > "$ns RPF-link $target [$upstreamtmp id] $tmp"
> > > (procedure "_o4827" line 33)
> > > (CtrMcastComp compute-branch line 33)
> > > invoked from within
> > > "$Agent compute-branch $s $group [$Node id]"
> > > (procedure "_o4970" line 27)
> > > (CtrMcast join-group line 27)
> > > invoked from within
> > > "$proto join-group $group"
> > > (procedure "_o3120" line 4)
> > > (McastProtoArbiter join-group line 4)
> > > invoked from within
> > > "$mcastproto_ join-group $group"
> > > (procedure "_o3116" line 5)
> > > (Node join-group line 5)
> > > invoked from within
> > > "_o3116 join-group _o5342 0x8000"
<http://www.ee.surrey.ac.uk/Personal/L.Wood/>PGP<[email protected]>