Page 1 of 1

ISIS extended IS/IP reachability

Posted: 03 Mar 2016 02:58
by moods
Hi,

doing some IOT between ALU and some other vendor and ISIS database is not populated on the other node (adjacency is up)

Does ALU by default send both "normal" and extended IS/IP reachability? I do not have traffic engineering enabled.

Code: Select all

A:ALU2>config>router>isis# info       
----------------------------------------------
            level-capability level-2
            area-id 10.0001
            interface "system"
                passive
                no shutdown
            exit
            interface "to_xxxx"
                interface-type point-to-point
                no shutdown
            exit
            no shutdown

Code: Select all

-------------------------------------------------------------------------------
LSP ID    : ALU2.00-00                                  Level     : L2  
Sequence  : 0x3                    Checksum  : 0x7f2f   Lifetime  : 696
Version   : 1                      Pkt Type  : 20       Pkt Ver   : 1
Attributes: L1L2                   Max Area  : 3        
SysID Len : 6                      Used Len  : 142      Alloc Len : 1492
                                      
TLVs : 
  Area Addresses:
    Area Address : (3) 10.0001
  Supp Protocols:
    Protocols     : IPv4
  IS-Hostname   : ALU2
  Router ID   :
    Router ID   : 22.22.22.22
  IS Neighbors  :
    Virtual Flag  : 0
    Default Metric: (I) 10
    Delay Metric  : (I) 0
    Expense Metric: (I) 0
    Error Metric  : (I) 0
    Neighbor      : 0000.0000.0003.00                   
  Internal Reach:
    Default Metric: (I) 10
    Delay Metric  : (I) 0
    Expense Metric: (I) 0
    Error Metric  : (I) 0
    IP Address    : 192.168.35.0
    IP Mask       : 255.255.255.0
    Default Metric: (I) 0
    Delay Metric  : (I) 0
    Expense Metric: (I) 0
    Error Metric  : (I) 0
    IP Address    : 22.22.22.22
    IP Mask       : 255.255.255.255
  I/F Addresses :
    I/F Address   : 192.168.35.2
    I/F Address   : 22.22.22.22
  TE IS Nbrs   :
    Nbr   : 0000.0000.0003.00                   
    Default Metric  : 10
    Sub TLV Len     : 12
    IF Addr   : 192.168.35.2
    Nbr IP    : 192.168.35.3
  TE IP Reach   :
    Default Metric  : 10
    Control Info:    , prefLen 24
    Prefix   : 192.168.35.0
    Default Metric  : 0
    Control Info:    , prefLen 32
    Prefix   : 22.22.22.22
Thanks for feedback

Re: ISIS extended IS/IP reachability

Posted: 07 Mar 2016 03:08
by thecandymancan
Which TLVs are you talking about?

Should be no issue with interop.

Re: ISIS extended IS/IP reachability

Posted: 07 Mar 2016 10:41
by mivens
I think you've sort of answered your own question. I believe you need traffic-engineering (and wide metrics) enabled for the extended IS reachability TLV.