From: mcaplan.cs@xxxxxxxxxxxxxxx
Date: Wed Jun 06 2001 - 09:50:41 GMT-3
I have just read CCO usage guide lines on internal network number. It makes
it quite clear that for NLSP to work, you have to use an internal network
number.
I'll probably get flamed anyway, but this is to acknowledge I was being
daft.
Usage Guidelines
An internal network number is a network number assigned to the router. This
network number must be unique within the internetwork.
You must configure an internal network number on each device on an
NLSP-capable network for NLSP to operate.
When you set an internal network number, the Cisco IOS software advertises
the specified network out all interfaces. It accepts packets destined to
that network at the address internal-network.0000.0000.0001.
> ----------
> From: TCN CAPLAN Mark - Service Provider
> Sent: Mittwoch, 6. Juni 2001 14:31
> To: 'ccielab@groupstudy.com'
> Subject: NLSP adjacency encapsulation failure on Token ring
>
> Can someone tell me whats going on here. I've got NLSP enabled between 2
> routers on a token ring segments. RIP works fine, and I can IPX ping
> across between the 2 routers.
>
> R2(to0)-------(to0)R4
>
> However, I have also enabled NLSP, but the adjacency doesn't come up.R2
> sits in the INIT state. A debug shows the following error on R2
>
> #R2
> *Mar 1 03:20:34.647: NLSP-Adj: Rec L1 IIH from 0000.30e2.6d0c
> (TokenRing0), cir type L1, cir id 0000.30E2.6D0C.04 (no-mc)
> *Mar 1 03:20:39.451: NLSP-Adj: Encapsulation failed for level 1 IIH on
> TokenRing0
>
> It looks like R2 receives the HELLO from R4, tries to form a packet and
> then fails to encapsulate it for some reason. I know about encaps problems
> on frame relay and how to get round it, but on Token ring I cant think
> what the problem could be.
>
>
> Just before I sent this e-mail out, I set up an internal network number on
> R2 and was surprised to suddenly see the adjacency come up, with no
> encapsulation failures. What has internal n/w number got to do with the
> HELLO packets. I thought that the HELLO packet contained the n/w of the
> link and the area address. If these 2 agree the adjacency should come up.
> Is this is a bug or am I missing something. I am using IOS 12.016.
>
> Any help would be appreciated
>
> Thanks
>
> Mark
>
> configs as follows:
>
> hostname r2
> !
> ipx routing 0008.dedc.9e93
> !
> interface TokenRing0
> mac-address 0000.0000.0002
> no ip address
> no ip directed-broadcast
> ipx network AAAA01
> ipx nlsp area2 enable
> ring-speed 16
> !
> ipx router nlsp area2
> area-address AAAA00 FFFFFF00
>
>
> hostname r4
> !
> ipx routing 0000.30e2.6d0c
> ipx internal-network 12340002
> !
> !
> interface TokenRing0
> no ip address
> no ip directed-broadcast
> ipx network AAAA01
> ipx nlsp area2 enable
> ring-speed 16
> !
> ipx router nlsp area2
> area-address AAAA00 FFFFFF00
> !
>
>
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE
Internet communications are not secure and therefore Clearstream International
does not
accept legal responsibility for the contents of this message.
The information contained in this e-mail is confidential and may be legally pri
vileged. It is
intended solely for the addressee. If you are not the intended recipient, any d
isclosure,
copying, distribution or any action taken or omitted to be taken in reliance on
it, is
prohibited and may be unlawful. Any views expressed in this e-mail are those of
the
individual sender, except where the sender specifically states them to be the v
iews of
Clearstream International or of any of its affiliates or subsidiaries.
END OF DISCLAIMER
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:19 GMT-3