OSPF v ISIS ?

Hi,
With IS-IS, an L1/L2 router will hold a Level 1 LSD and a level 2 LSD and two separate SPF calculations are run for the L1 routes and the L2 routes.
With OSPF lets say that an ABR has two Areas connected e.g Area 0 and Area 1, then the router will hold separate LSA's for each of these Areas.
My question is: Will the SPF algorithm be run once or twice ?

Hello,
I dont know the in depths of SPF calculation. But, I believe SPF is used to calculate the best route to a network and put this is the routing table. So , it would need all information (lsa) from all areas to do so.
So, I'd say its only 1 SPF calculation.
HTH,
if it does, please rate this post.
Vlad

Similar Messages

  • Why OSPF is not used in MPLS, though it is very efficient protocol

    Dear all, though OSPF is a very efficient protocol, with a number of features to handle much larger networks,it is not used in MPLS. Can u plz let me know, what special features BGP posses over OSPF, for its selection in MPLS.

    For core MPLS switching, any routing protocol can be used, including static. Service providers have preferred to use link state protocol like OSPF and ISIS and they still do.
    However, different MPLS applications have their routing protocol requirements. MPLS Traffic Engineering for example requires a link state protocol. Hence, if you want to do Traffic Engineering, your IGP must be either OSPF or ISIS. This is because for proper operation of MPLS TE, the routers should have a complete topology view of the network, so as to be able to route packet accordingly.
    For MPLS VPN, there is a requirement to deploy iBGP on the edge routers. The main requirement stems from label allocation procedure of MPLS. While MPLS routers assigns a label for every route in the FIB, routes learned via BGP are exempted. Rather, for BGP learnt routes, the label for the BGP next-hop of the route is used. This is critical to the operation of the MPLS VPN, because it effectively creates a tunnel and ensures that every router on the network does not have to carry all the VPN routes.
    I hope the explanation is clear

  • %ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21

    hi,
    why this log message keep appearing??
    RP/0/RSP0/CPU0:9010-2#
    RP/0/RSP0/CPU0:9010-2#RP/0/RSP0/CPU0:Oct  8 14:50:37.023 : isis[1001]: %ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21 will not be used
    RP/0/RSP0/CPU0:9010-2#
    On both side hello padding is disable for level 2.
    interface Bundle-Ether22
      circuit-type level-2-only
      point-to-point
      hello-padding disable level 2
      hello-password keychain ISIS-key
      address-family ipv4 unicast
       metric 10 level 2
       mpls ldp sync level 2
    regards
    tahir

    Router 1 config outup:
    RP/0/RSP0/CPU0:9010-1#sh run int bundle-ether 12
    Tue Oct  9 14:26:10.591 KSA
    interface Bundle-Ether12
    description "EtherChannel to 9010-2"
    mtu 9216
    service-policy output EGRESS-NNI
    ipv4 address 10.0.1.30 255.255.255.252
    ipv4 unreachables disable
    bundle minimum-active links 1
    bundle minimum-active bandwidth 10000000
    load-interval 30
    dampening
    RP/0/RSP0/CPU0:9010-1#show isis interface bundle-ether12
    Tue Oct  9 14:25:56.600 KSA
    Bundle-Ether12              Enabled
      Adjacency Formation:      Enabled
      Prefix Advertisement:     Enabled
      BFD:                      Disabled
      BFD Min Interval:         150
      BFD Multiplier:           3
      Circuit Type:             level-2-only
      Media Type:               P2P
      Circuit Number:           0
      Extended Circuit Number:  134218016
      Next P2P IIH in:          9 s
      LSP Rexmit Queue Size:    0
      Level-2                  
        Adjacency Count:        1
        LSP Pacing Interval:    33 ms
        PSNP Entry Queue Size:  0
      CLNS I/O
        Protocol State:         Up
        MTU:                    9199
        SNPA:                   b414.89e0.9f99
        Layer-2 MCast Groups Membership:
          All ISs:              Yes
      IPv4 Unicast Topology:    Enabled
        Adjacency Formation:    Running
        Prefix Advertisement:   Running
        Metric (L1/L2):         10/10
        MPLS LDP Sync (L1/L2):  Disabled/Enabled
          Sync Status:          Achieved
      IPv4 Address Family:      Enabled
        Protocol State:         Up
        Forwarding Address(es): 10.0.1.30
        Global Prefix(es):      10.0.1.28/30
      LSP transmit timer expires in 0 ms
      LSP transmission is idle
      Can send up to 9 back-to-back LSPs in the next 0 ms
    RP/0/RSP0/CPU0:9010-1#
    RP/0/RSP0/CPU0:9010-1#
    RP/0/RSP0/CPU0:9010-1#sh run router isis
    Tue Oct  9 14:26:41.010 KSA
    router isis core
    net 49.0001.0100.0000.0003.00
    nsf cisco
    lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
    lsp-refresh-interval 65000 level 2
    max-lsp-lifetime 65535 level 2
    address-family ipv4 unicast
      metric-style wide
      spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
      redistribute static route-policy STATIC-TO-ISIS
      redistribute ospf 100 route-policy RP-FROM-OSPF-TO-ISIS
    interface Bundle-Ether12
      circuit-type level-2-only
      point-to-point
      hello-padding disable level 2
      hello-password keychain ISIS-key
      address-family ipv4 unicast
       metric 10 level 2
       mpls ldp sync level 2
    Router 2 output config:
    RP/0/RSP0/CPU0:9010-2#sh run int bundle-ether 21
    Tue Oct  9 14:24:11.346 KSA
    interface Bundle-Ether21
    description "EtherChannel to 9010-1
    mtu 9216
    service-policy output EGRESS-NNI
    ipv4 address 10.0.1.29 255.255.255.252
    bundle minimum-active links 1
    bundle minimum-active bandwidth 10000000
    dampening
    RP/0/RSP0/CPU0:9010-2#
    RP/0/RSP0/CPU0:9010-2#show isis interface bundle-ether21
    Tue Oct  9 14:23:48.457 KSA
    Bundle-Ether21              Enabled
      Adjacency Formation:      Enabled
      Prefix Advertisement:     Enabled
      BFD:                      Disabled
      BFD Min Interval:         150
      BFD Multiplier:           3
      Circuit Type:             level-2-only
      Media Type:               P2P
      Circuit Number:           0
      Extended Circuit Number:  134218208
      Next P2P IIH in:          6 s
      LSP Rexmit Queue Size:    0
      Level-2                  
        Adjacency Count:        1
        LSP Pacing Interval:    33 ms
        PSNP Entry Queue Size:  0
      CLNS I/O
        Protocol State:         Up
        MTU:                    9199
        SNPA:                   0026.980e.d3e2
        Layer-2 MCast Groups Membership:
          All ISs:              Yes
      IPv4 Unicast Topology:    Enabled
        Adjacency Formation:    Running
        Prefix Advertisement:   Running
        Metric (L1/L2):         10/10
        MPLS LDP Sync (L1/L2):  Disabled/Enabled
          Sync Status:          Achieved
      IPv4 Address Family:      Enabled
        Protocol State:         Up
        Forwarding Address(es): 10.0.1.29
        Global Prefix(es):      10.0.1.28/30
      LSP transmit timer expires in 0 ms
      LSP transmission is idle
      Can send up to 9 back-to-back LSPs in the next 0 ms
    RP/0/RSP0/CPU0:9010-2#
    RP/0/RSP0/CPU0:9010-2#sh run router isis
    Tue Oct  9 14:24:41.457 KSA
    router isis core
    net 49.0001.0100.0000.0002.00
    nsf cisco
    log adjacency changes
    lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
    lsp-refresh-interval 65000 level 2
    max-lsp-lifetime 65535 level 2
    address-family ipv4 unicast
      metric-style wide
      spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
    interface Bundle-Ether21
      circuit-type level-2-only
      point-to-point
      hello-padding disable level 2
      hello-password keychain ISIS-key
      address-family ipv4 unicast
       metric 10 level 2
       mpls ldp sync level 2

  • Moving from L2 network to L3.

    Hi guys,
    Recently i have start working to a small Service Provider and we are delivering ethernet leased lines to the end customer.
    Our network is consisted of many ME 3600X and one 7609-S. The interconnections for all these are made by microwave point to point links (relay points) and for customer ethernet service we are using point to multipoint links (base stations) . In the attachement you can see the network topology.
    The network is configured as a Layer 2 which meens that all point to point links are configured as Trunks with service intances.
    There are no redundant links and Spanning Tree is not currently in use.
    To add a customer we are creating a new vlan on ME 3600X and we are assigning that vlan to an access port, the vlan is added to whole path of ME switches and in the 7609-S we are creating service instance, vlan and interface vlan.
    Sample Configuration
    Ending ME 3600X
    vlan 503
    name TEST
    interface giga0/5
    description TEST
    switchport access vlan 503
    Middle  ME 3600X
    vlan 503
    name TEST
    7609-S
    bridge-domain 503
    vlan 503
    name TEST
    interface giga 0/5
    service instance 503 ethernet
    encapsulation dot1q 503
    rewrite ingress tag pop1 symmetric
    brigde-domain 503 split-horizon
    interface Vlan503
    description TEST
    ip address xxx.xxx.xxx.xxx 255.255.255.252
    no ip redirects
    no ip unreachables
    We are in progress of buying a second Cisco 7609-S for redundancy and some ME 3600X for network expansion and probably there will be redundant point to point links. To make our netwotk more effiecient and scalable we would like to move on from L2 to L3.
    One question is to setup SVIs on MEs and add them to the routing process or is more preferable to use pure L3 ports to point to point links?
    Second question is regarding which protocol to use ISIS or OSPF?
    In case of enabling a routing process is there any resone to use MC-LAG to 7609s ?
    And last one. Is there something to watch out, so that customers don't exerience service interruption?
    Thank you in advance.

    You could have point-to-point L3 links between ME3600 and 7600 (with OSPF or ISIS).
    And On ME3600 you could have this config :
    vlan 503
    name TEST
    interface giga0/5
    description TEST
    switchport access vlan 503
    interface Vlan503
    description TEST
    ip address xxx.xxx.xxx.xxx 255.255.255.252
    no ip redirects
    no ip unreachables
    You can redistribute your customers subnet with redistrubute connected or with passive-interface on OSPF/ISIS.

  • Routing Protocol recommendation for MPLS Network

    I am in the process of building a 14 site MPLS network for voice and data traffic. The vendor installing the network has configured RIPv2 as the routing protocol. I am considering switching this over to EIGRP. Can anyone explain to me why this would be better or should I just stay with RIP.
    Thanks

    Hi Chip,
    Its not very clear whether you are implementing a MPLS network or implementing a Network over MPLS for an end user with 14 sites.
    1) If MPLS network then other IGP variants than OSPF and ISIS best avoided. Now if the choice is between ISIS and OSPF then my personal recommendation would be OSPF. And this decision is purely driven by Operational Considerations rather than any technical advantages. Since at the end of the day what matters is how easy it is to implement add delete or troubleshoot the network.
    2)If for End User then it would not be right to recommend EIGRP or RIP or OSPF without knowing the current size & topology of each of these 14 sites, as well as the desired expansion plans. But if these 14 sites are the only sites and are all standalone branch sites connecting over MPLS VPN then RIP,EIGRP or OSPF can be implemented as per your and customer comfort.
    HTH-Cheers,
    Swaroop

  • MPLS L3VPN

    Hello Everyone,
    I also posted this at the Cisco Learning Network, but I thought I post it here too.
    I am learning MPLS L3VPN and its components.  I thought I had a grasp on the VRF table and where it is located (at the respective PE router interconnecting to the customer).  However, today at work while using Packet Design Route Explorer, I could see the VRF appear at the P routers.  This really confused me. 
    I brought this up to one of the more experienced Engineers and she stated that the VRF table will be propagated through the network.  I got even more consured.
    My understanding is that respective customer routes are kept in the VRF table and redistributed (for us it is BGP) at the PE router.  The uniqueness of the routes are based on the RT (route targets) that are part of the extended community.  Once it gets into the core it moves along like other packets.
    So my bottom line question are there respective VRF tables in the P routers?  Or as my co-worker told me, the VRF tables are forwarded through the network.
    If my view of a VRF table (i.e. only present at the PE router) is correct, then my question will be to Packet Design on what I am viewing.
    I guess when I see the term "VRF" refers to the table defined and created at the PE router.
    Any help on this matter will be appreciated.
    Aloha,
    Mike

    just in very brief as this subject has many to read and understand about
    the Core network between ( P ) routes use label switching based on IGP routing table such as OSPF or ISIS
    for building next hoe and labels ( labels are locally significant values only ) each PE reach other PEs over the Core/P uses MPLS/with label switching/forwarding
    however each PE has VRFs and other routing and route leaking polices and IGP or BGP with CEs all redistributed in relevant VRF/MP-BGP routing table that uses RD/RT for route isolation and these routes of VRfs exchanged between PEs using BGP VPNv4 which is not known to the P routers
    simply PE---MPLS---P---MPLS---PE
    CE---VRF---MPBGP/VPNv4---PE---MPLS---P---MPLS---PE---MPBGP/VPNv4---VRF---CE
    HTH
    if helpful Rate

  • MPLS TE - Latency

    Is TE able to detect high latency on a circuit? I understand is solve problems like efficient use of all avaliable bandwidth based on RSVP but how about long distant links with increasing latency over time? Will TE detect that?

    Hello Francisco,
    the answer should be negative.
    With MPLS TE you can associate resources to links (RSVP bandwidth ) and you can run a modified version of OSPF or ISIS that takes in account current usage of these resources over the links, but not performance related info about the links.
    For that you should look at OER / Performance routing where you can "test" the links over time and you can decide to stop to use links that are beyond a threshold.
    And of course QoS can be of great help in providing better treatment to some traffic classes (so bounded latency and limited jitter)
    What kind of WAN links are you meaning ?
    Hope to help
    Giuseppe

  • Fast-reroute: failure detection on ATM

    Hi,
    I have read in Designing MPLS TE Networks book that in essence fast-reroute feature failure detection of under 50ms is possible on pure POS interfaces and not possible on ATM interfaces which might also be runnig over POS.
    I have noticed a command that had been available since 12.1T - "oam ais-rdi". According to this command description, it is possible to bring down ATM PVC after receiving one AIS indicating cell.
    Isn't that exactly how it works on POS?
    Was this Ciscopress book so much outdated or am I missing something?
    Thanks,
    David

    Hello,
    there is a major difference (on a ms time scale) in POS and in ATM AIS. With POS interfaces one utilizes the error indication in the SONET/SDH frame. This means the first frame after failure detection of end OR intermediate systems (muxer) will contain the error bits needed to bring down the interface and trigger fast reroute.
    If you look into an ATM solution, then only ATM equipment will be able to insert ATM cells for failure indication. This means a mux will not be able to indicate anything. Only ATM switches or end devices might "help" out, but for them failure detection is maybe bound to keepalives as well.
    So you MIGHT get very low recovery times, but you could also have failure conditions only detectable by keepalive mechanisms. The latter are slower than in POS.
    Once you are relying on keepalives you could also use subsecond keepalives with OSPF or ISIS to achieve pretty fast recovery times.
    Hope this helps! Please rate all posts.
    Regards, Martin

  • Configuring LSP

    Hi All,
         I need to know the set of commands which are needed to create new LSP in Cisco Router.
    I  tried searching other docs available on Cisco Support forums, and came  across the below set of commands, please help me know if these are  correct and sufficient .
    Also please guide me to know commands needed to create Explicit Path LSP.
    switch# configure terminal
    switch(config)#
    switch(config)# feature mpls traffic-engineering
    switch# configure terminal
    switch(config)#
    switch(config)# feature isis
    switch(config)# router isis 200
    switch(config-router)#
    switch(config-router)# mpls traffic-eng level-1
    switch(config-router)# mpls traffic-eng router-id loopback0
    switch# configure terminal
    switch(config)#
    switch(config)# feature ospf
    switch(config)# router ospf 200
    switch(config-router)#
    switch(config-router)# mpls traffic-eng area 1
    switch(config-router)# mpls traffic-eng router-id loopback0
    switch# configure terminal
    switch(config)#
    switch(config)# interface ethernet 2/1
    switch(config-if)#
    switch(config-if)# mpls traffic-eng tunnels
    switch(config-if)# mpls traffic-eng bandwidth 1000
    switch(config-if)# no shut
    switch# configure terminal
    switch(config)#
    switch(config)# interface tunnel-te 1
    switch(config-if-te)#
    switch(config-if-te)# ip unnumbered loopback 0
    switch(config-if-te)# destination 10.3.3.3
    switch(config-if-te)# path-option 10 explicit name Link5
    switch(config-if-te)# no shutdown
    switch# configure terminal
    switch(config)#
    switch(config)# mpls traffic-eng configuration
    switch(config-te)#
    switch(config-te)# explicit-path name Link5
    switch(config-te-expl-path)# index 10 next-address 10.3.3.3

    Hello Ayush,
    To form the LSP using MPLS Traffic Engineering, folowing is the checklist:
    ++ CEF should be enabled on all the routers
    config t
    ip cef
    ++ Loopback should be configured on the routers (which will also be used as router-id)
    ++ End to end loopback reachability should be fine via ISIS or ospf
    ++ "mpls traffic-eng tunnel" should be configured globally
    ++ "mpls traffic-eng tunnel" and "ip rsvp bandwidth" should be configured under all the core interfaces. By default rsvp reserves 75% bandwidth
    ++ mpls traffic-engineering should be configured under the ospf or isis process (as seen in the output of your question)
    switch(config)# router ospf 200
    switch(config-router)#
    switch(config-router)# mpls traffic-eng area x
    switch(config-router)# mpls traffic-eng router-id loopback0
    ++ Configure the explicit path on 2 end points
    Suppose you have 3 routers:
    A---------B---------C
    so the config on A will be:
    ip explicit-path name ABC
    next-address
    next-address
    next-address
    Similarly, configure the explicit path on C in reverse direction.
    ++ Finally, configure the tunnel on 2 end points.
    config t
    int tunnel x
    ip unnumbered loop0
    tunnel mode mpls traffic-eng
    tunnel destination x.x.x.x >> This is the loopback IP of remote end
    tunnel mpls traffic-eng path-option 1 explicit name abc
    After this, it is upto you if you want to send the traffic on this tunnel via this options:
    1. static
    2. PBR
    3. Autoroute Announce
    4. Forwarding Adjacency
    5. Load Sharing
    6. Automatic Bandwidth Adjustment
    Seems like the command line you used above is for Nexus (NX-OS). I have explained it for IOS.
    Hope This Helps!!
    Regards,
    Imran

  • Can I use EIGRP as a MPLS Backbone IGP

    Hi,
    Always believed MPLS only runs on IS-IS and OSPF as backbone IGP. Is it possible to use EIGRP as a backbone IGP as well?
    My customer uses EIGRP right now and we want to migrate VRF-lite to a real MPLS cloud. Can I re-use EIGRP?
    Best regards,
    Peter

    Hi Peter,
    For plain MPLS, there is no restriction that you need OSPF or ISIS. But when you plan to implement MPLS TE, you need a link state protocol. So if you dont have any plan to go for Traffic Engg, I think you can continue with EIGRP.
    HTH,
    Nagendra

  • IOS XR

    Hello:
    Which Cisco router platforms use IOS XR?
    Is it just the CRS-1, ASR 9000 and GSR 12000? What about the asr 1000?
    What is the big difference between regular IOS and IOS XR?
    What is the ASR 9000 used for? WAN edge? SP PE? SP core?
    So for so many questions...
    Thanks

    Hello Joe,
    IOS XR is supported on CRS and GSR 12000 XR and ASR 9000
    see
    http://www.cisco.com/en/US/products/ps5845/products_installation_and_configuration_guides_list.html
    about different IOS flavors:
    http://www.cisco.com/en/US/products/ps6350/products_white_paper09186a0080b1351e.shtml
    ASR 1000 supports IOS XE and Nexus supports NX-OS
    IOS XR has a different architecture then IOS: it uses a real-time microkernel OS that provides basic services.
    Over this common layer other SW layers are added for example OSPF or ISIS module, MPLS module and so on.
    It is not a monolithic image, but rather it has a unix derived approach. Modularity provides also for the capability to perform partial updates of one or more SW modules. They are called SMU.
    IOS XR is designed with service provider carrier class needs
    ASR 9000 is designed for PE role and aggregation services and it is a young platform.
    http://www.cisco.com/en/US/prod/collateral/routers/ps9853/data_sheet_c78-501767.html
    to be noted also an ASR 14000 has been introduced recently but I cannot find info about it.
    Hope to help
    Giuseppe

  • MPLS TE tunnel autoroute announce metric in SPF computation

    Hi, I have a doubt whether MPLS TE tunnel metric is taking into SPF computation when the tunnel has "autoroute announce" configured.
    From the book "MPLS traffice enginnering" written by Osbourn, IGP SPF computation is always performed before tunnel metric is modified, I found this is only true if IGP is ISIS, but if IGP is OSPF, tunnel metric specified by "autoroute metric" will always be taken into SPF computation, a.k.a, if tunnel metric is configured to be less than underlying IGP metric, a suboptimal routing will always happen to destination routers that are in between tunnel head and tunnel tail.
    Any idea why there is a inconsistent behavior between OSPF and ISIS SPF computation? or I missed anything?

    Hi,
    You're right. There is a different behavior between OSPF and ISIS on how they handle the autoroute metric feature.
    ISIS: TE tunnel metric is not taken into account during SPF computation.
    OSPF: TE tunnel metric is taken into account during SPF computation.
    So playing with this feature can change the SPT if your IGP is OSPF.
    The difference seems coming from the SPF implementation of OSPF and ISIS
    HTH
    Laurent.

  • Maximum ip routes that can be handled by isis and ospf

    Hello All,
    Is there any limitation on the number of ip routes that isis can handle? I was going through one of the documentations which mentioned that the limit is 30K routes. This is due to the max number of fragments ( 256 ) with each containing not more than 121 routes.?
    Do the following commands  help to change this number?
    lsp-mtu
    and clns-mtu
    Has anyone seen any such limitation for OSPF ?
    Regards,
    Shreeram

    Hello Shreeram,
    Hmm Qestion is quit logical, But what can I say is, believe me OSPF can handle lot of routes. It completly depends upon your Routers Processor and Memory.
    In no I can say more than 6000 routes (reference https://supportforums.cisco.com/thread/10496)
    For OSPF not to suffer, we must follow some rules when we make areas, it is because it is a linkstate algorithm, below are the same
    for more information you can browse here
    http://www.ciscopress.com/articles/article.asp?p=1763921&seqNum=6
    Factors Influencing OSPF Scalability
    Scaling is determined by the utilization of three router resources: memory, CPU, and interface bandwidth. The workload that OSPF imposes on a router depends on these factors:
    Number of adjacent neighbors for any one router: OSPF floods all link-state changes to all routers in an area. Routers with many neighbors have the most work to do when link-state changes occur. In general, any one router should have no more than 60 neighbors.
    Number of adjacent routers in an area: OSPF uses a CPU-intensive algorithm. The number of calculations that must be performed given n link-state packets is proportional to n log n. As a result, the larger and more unstable the area, the greater the likelihood for performance problems associated with routing protocol recalculation. Generally, an area should have no more than 50 routers. Areas that suffer with unstable links should be smaller.
    Number of areas supported by any one router: A router must run the link-state algorithm for each link-state change that occurs for every area in which the router resides. Every ABR is in at least two areas (the backbone and one adjacent area). In general, to maximize stability, one router should not be in more than three areas.
    Designated router (DR) selection: In general, the DR and backup designated router (BDR) on a multiaccess link (for example, Ethernet) have the most OSPF work to do. It is a good idea to select routers that are not already heavily loaded with CPU-intensive activities to be the DR and BDR. In addition, it is generally not a good idea to select the same router to be the DR on many multiaccess links simultaneously.
    Please rate the helpful posts
    Regards
    Thanveer
    "Everybody is genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is a stupid."

  • Can cisco router support OSPF-TE and ISIS-TE same time for CSPF to compute a TE LSP? I may need to run both IGP in parreral.

    Can cisco router support OSPF-TE and ISIS-TE same time for CSPF to compute a TE LSP? I may need to run both IGP in parreral.

    hello - I have just moved your post to the Topic forums - you had posted your question in an obscure non-visible promotional community  Hopefully our community users will see your question now.

  • Can cisco router support OSPF-TE and ISIS-TE same time for CSPF to compute a TE LSP? I may need to run both IGP in parallel

    Can cisco router support OSPF-TE and ISIS-TE same time for CSPF to compute a TE LSP? I may need to run both IGP in parallel.

    Hi Johnny,
    Per my understanding you can. It is equivalent to running 2 IGP and installing the entry in RIB table based on administrative distance. 
    -Nagendra

Maybe you are looking for