[j-nsp] ISIS adjacency on the GigE interface

Dave McGaugh dmcgaugh at cac.washington.edu
Mon Jun 13 15:48:24 EDT 2005


I'm not an ISO expert, but here goes :)
You might try changing the AFI from 99 to 49. Some docs I've read  
seem to suggest that the AFI is, among other things responsible for  
defining the addressing format. I'm not sure whether JunOS enforces  
such a thing, but if your addressing structure conflicts with that  
which is defined for AFI 99, it could create problems..

-Dave

On Jun 13, 2005, at 10:16 AM, Johnny Kui wrote:

> Hi Sorin,
>
> I went ahead and set the mtu on the interface. The show commands  
> show the correct MTU:
>
>
>> show configuration interfaces ge-1/2/0.0 family iso
>>
> mtu 1497;
>
>
>> show interfaces ge-1/2/0.0 media | match iso
>>
>     Protocol iso, MTU: 1497
>
> But the adjacency is still not coming up.
>
> Thanks,
> John
>
>
> Sorin CONSTANTINESCU <adonay at gtstelecom.ro> wrote:
> Hi,
>
> Take care to the CLNS MTU for the GE Interface. ISIS paddes the ISIS
> hello packet to the MTU of the GE.
>
> You can set the MTU for CLNS on the interface to a value usable by the
> other routers' interfaces:
>
>
>> show interfaces ge-0/0/0.11 media | match iso
>>
> Protocol iso, MTU: 1497
>
>
>> show configuration interfaces ge-0/0/0.11 family iso
>>
> mtu 1497;
>
> Regards,
> --
> Sorin
>
> Johnny Kui wrote:
>
>> Hi,
>>
>> I am having problem to establish ISIS L2 adjacency on the M10 GigE  
>> interface. But using the same configuration, I can set up L2  
>> adjacency on the FastE interface. When turn on the traceoptions, I  
>> can only see the M10 sending out hello packets but not receiving  
>> any hello packets. Am I missing any configurations on the GigE  
>> interface? The Juniper M10 is running version 6.2R1.5.
>>
>> interfaces {
>> ge-1/2/0 {
>> enable;
>> unit 0 {
>> enable;
>> family inet {
>> address 124.123.122.2/30
>> }
>> family iso;
>> }
>> }
>> lo0 {
>> unit 0 {
>> family inet {
>> no -redirects;
>> address 120.120.120.120/32
>> }
>> family iso {
>> address 99.0001.1234.5678.1111.00;
>> }
>> }
>> }
>> }
>> protocols {
>> isis {
>> no-ipv6-routing;
>> level 1 disable;
>> level 2 {
>> no-hello-authentication;
>> no-csnp-authentication;
>> no-psnp-authentication;
>> }
>> interface all {
>> level 1 disable;
>> }
>> interface fxp0.0 {
>> disable;
>> }
>> }
>> }
>>
>> The other end of the GigE connection has IP address  
>> 124.123.122.1/30. The loopback has IP address 20.20.20.20/32. The  
>> ISO address is 99.0001.1600.3333.4444.0, and is configured with L2  
>> enabled.
>>
>> Thanks,
>> John
>>
>>
>>
>> ---------------------------------
>> Discover Yahoo!
>> Find restaurants, movies, travel & more fun for the weekend. Check  
>> it out!
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>



More information about the juniper-nsp mailing list